Re: Is this pgbouncer configuration suitable for aproduction environment with hundreds of databases? - Mailing list pgsql-general

From David G. Johnston
Subject Re: Is this pgbouncer configuration suitable for aproduction environment with hundreds of databases?
Date
Msg-id CAKFQuwb=a41q-07GXd-4j8dqrRNOvPchSUX0nVzjo4EmFO7i8A@mail.gmail.com
Whole thread Raw
In response to Is this pgbouncer configuration suitable for a productionenvironment with hundreds of databases?  (Lisandro <rostagnolisandro@gmail.com>)
Responses Re: Is this pgbouncer configuration suitable for a productionenvironment with hundreds of databases?  (Lisandro <rostagnolisandro@gmail.com>)
List pgsql-general
On Wed, Apr 5, 2017 at 3:29 PM, Lisandro <rostagnolisandro@gmail.com> wrote:

The question is: can I set default_pool_size=0

​ISTM parameter would be better named (i.e., mentally remembered as) "default_maximum_pool_size" ... and a zero for that seems like you'll render your system inoperable since:

"Notice that I don't set a pool_size for every database, but instead I use
the general default_pool_size.

> *My goal is to find a pgbouncer configuration that allows me to add
> databases without worring about reaching the postgresql max_connection=200
> limit. How can I achieve that?*

The presence of open issue # 103 on GitHub implies that what you want to do is not possible.


David J.

pgsql-general by date:

Previous
From: Lisandro
Date:
Subject: Is this pgbouncer configuration suitable for a productionenvironment with hundreds of databases?
Next
From: Lisandro
Date:
Subject: Re: Is this pgbouncer configuration suitable for a productionenvironment with hundreds of databases?