PostgreSQL how to increase limit connections?

[Aleksander Efremov]

I found what for PostgreSQL was set max limit connections in 100.

I use several cloud functions which try to receive a part of this limit of connections.

But often there is a situation when two functions receive all limit of connections and for the other functions the limit already is exhausted.

Pool for connections there is no opportunity to use because every function executes in own isolate environment.

[Vladimir Rusinov]

There is currently no way to do so, but it is something we'd like to address in future.

Please follow this feature request: https://issuetracker.google.com/issues/37271935

As a temporary workaround, you can run something like pgbouncer on Compute Engine in the same region as your instance.

--
Vladimir Rusinov
PostgreSQL SRE, Google Ireland

Google Ireland Ltd.,Gordon House, Barrow Street, Dublin 4, Ireland
Registered in Dublin, Ireland
Registration Number: 368047

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/943fcddc-cfa8-4c57-91a3-ce5bbadc1f49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aleksander Efremov]

Thank you.

четверг, 13 апреля 2017 г., 18:19:05 UTC+4 пользователь Vladimir Rusinov написал:

[Fahad G]

As a temporary workaround, you can run something like pgbouncer on Compute Engine in the same region as your instance.

Can we do the same on a normal flex App Engine environment? If so, any steps / setup guide as reference? Thanks! 

[Thomas Yager-Madden]

On Thursday, April 13, 2017 at 9:19:05 AM UTC-5, Vladimir Rusinov wrote:

As a temporary workaround, you can run something like pgbouncer on Compute Engine in the same region as your instance.

Can you explain or point to documentation on how to use pgbouncer with Cloud SQL Postgres instance? Specifically, it seems that for authorizing users, pgbouncer needs access to pg_shadow, which is only available to superusers. 

[dvd gsng]

Hi Thomas, did you manage to set this up eventually using pg_shadow with CloudSQL? If not, how did you work around this shortcoming? Thanks!