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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lisandro <rostagnolisandro(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: GMT FATAL: remaining connection slots are reserved for non-replication superuser connections, but I'm using pgBouncer for connection pooling
Date: 2017-02-28 14:07:19
Message-ID: 2136.1488290839@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Lisandro <rostagnolisandro(at)gmail(dot)com> writes:
> 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.

You could enable log_connections and log_disconnections.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2017-02-28 14:33:24 Re: Question about TOAST table - PostgreSQL 9.2
Previous Message Lisandro 2017-02-28 14:01:06 Re: GMT FATAL: remaining connection slots are reserved for non-replication superuser connections, but I'm using pgBouncer for connection pooling