lay 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-configur
tgres limit? Is that suitable?
*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?*
Thanks in advance!
Regards,
Lisandro.
--
View this message in context:
http://www.postgresql
Hi Steve, thanks for your help.
Your comment made me realise that maybe the problem is my pgBouncer
configuration, specifically default_pool_size. It took me a while to
understand pgbouncer, and I still had some doubts when I configured it. Now
I undesrtand better.
I connect to all databases wit
of postgresql
connections through time.
Any comment or suggestion will be appreciated.
Thank you very much for your time!
Best regards,
Lisandro.
--
View this message in context:
http://www.postgresql-archive.org/GMT-FATAL-remaining-connection-slots-are-reserved-for-non-replication-superuser
02-25 12:17 GMT-03:00 Adrian Klaver-4 [via PostgreSQL] <
ml-node+s1045698n5946254...@n3.nabble.com>:
> On 02/25/2017 04:19 AM, lisandro wrote:
>
> > Hi there! Please tell me if this isn't the place to post my question,
> I'm new
> > in the list.
> >
Hi there! Please tell me if this isn't the place to post my question, I'm new
in the list.
I'm using PostgreSQL 9.3, I have around 150 databases, and I use pgBouncer
for connection pooling.
My server is a VPS with 8cpus and 24gb of RAM.
My current postgreSQL configuration (resumed) is this:
li
