Re: Is this pgbouncer configuration suitable for a production environment with hundreds of databases?

From: Lisandro <rostagnolisandro(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Is this pgbouncer configuration suitable for a production environment with hundreds of databases?
Date: 2017-04-05 23:33:25
Message-ID: 1491435205529-5954499.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thank you very much David for your quick reply, I understand better now.

For now, I'll let default_pool_size=2 and I guess I will have to monitor the
total number of databases and adjust configuration when needed, in order to
avoid reaching the postgres max_connection limit.

I think I can play a bit with some pgbouncer configuration directives, like
pool_size (per database), server_idle_timeout, server_connect_timeout and
idle_transaction_timeout.

Thanks for the help!
Regards,
Lisandro.

--
View this message in context: http://www.postgresql-archive.org/Is-this-pgbouncer-configuration-suitable-for-a-production-environment-with-hundreds-of-databases-tp5954479p5954499.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message George Neuner 2017-04-06 01:40:06 Re: browser interface to forums please?
Previous Message Andres Freund 2017-04-05 23:14:53 Re: [GENERAL] C++ port of Postgres