Re: Re: GMT FATAL: remaining connection slots are reserved for non-replication superuser connections, but I'm using pgBouncer for connection pooling

On 02/28/2017 06:01 AM, Lisandro wrote:
> Thank you Adrian.
>
> Yes, I confirm that all the databases are running in one PostgreSQL
> server/instance. I'm running this version:
> PostgreSQL 9.3.15 on i686-pc-linux-gnu, compiled by gcc (Ubuntu
> 4.8.4-2ubuntu1~14.04.3) 4.8.4, 32-bit
>
> Let me ask: is there a way to monitor the total connections to postgresql
> through time? Or should I make my own script for that? I ask because every
> time the error is thrown, I check the total connections with "select
> count(*) from pg_stat_activity;" but the number is always far from the
> configured max_connections.

I have not used any as my needs are fairly simple. All I can do is point
you at:

https://wiki.postgresql.org/wiki/Monitoring

Hopefully someone with more experience with this can help you out.

A question I forgot to ask previously:

Is there any app/client that uses the server that is not going through
pgBouncer?

>
>
> Maybe the problem is with pgBouncer, so I'll post this issue in their forum.
> I'm not really a sysop, so it's hard for me to fully understand the issue.
> The strange part is that the error appears in random hours, I mean, it
> doesn't correspond with the hours of higher db activity. Instead, the error
> appears in both scenarios: with high db activity and with very low db
> activity.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com