Fatal Remaining Connection Slots Are Reserved

admin

On Tue, Feb 7, 2017 at 6:52 PM, Patrick B <patrickbakerbr(at)gmail(dot)com> wrote:

Fatal remaining connection slots are reserved for non-replicationReserved

Azure Fatal Remaining Connection Slots Are Reserved For Non-replication Superuser Connections

> Hi guys,
>
> I get these messages at least once a day in my Prod environment:
>
>> FATAL: remaining connection slots are reserved for non-replication
>> superuser connections
>
> I do not have a DB pooler and my max_connections is 200. However, max
> connections for my PHP Application is 120.
>
> My server has 128GB and SSD 10K iops disks (Amazon EBS).
>
>
> Can you guys please outlines me the steps to troubleshoot this?
>
> Interesting is that I didn't see any IO/CPU limitation on my server.
>
> I'm currently running a Postgres 9.2 - one master and one slave streaming
> replication.
>
>
> Thanks
>
> Patrick
>

2012-06-13 13:45:38.895 MDT 25174: 1-1 FATAL: remaining connection slots are reserved for non-replication superuser connections Could it be that there are already maxconnections sessions? Maxconnection was set to 600, when issue occurred the db server had 85 connection and server was under medium load. FATAL: remaining connection slots are reserved for non-replication superuser connections. This is one of the first major operational problems that new users are likely to encounter with Postgres, and one that might prove to be frustratingly persistent.

Something is using too many connections.

I may be wrong but I'm unaware of a limit on connections from PHP except
when you are using persistent connections. Since each PHP script is it's
own process, it can create one or more connections. I'd check to be sure
that every PHP script you have is, indeed, using pg_pconnect and not
pg_connect. That missing 'p' could be hard to spot. I'm assuming, of
course, that you are sure that your PHP script are the only things that can
connect - no scripts, backups, etc. are consuming connections.

Pgadmin Fatal Remaining Connection Slots Are Reserved For Non-replication Superuser Connections

Confluence Fatal Remaining Connection Slots Are Reserved For Non-replication Superuser Connections

But generally I'd advise using pg_bouncer or a similar pooler which can
deal with a mix of connections from persistent and non-persistent
connections from one or multiple hosts.

Fatal Remaining Connection Slots Are Reserved For Non-replication Superuser Connections Aws

Cheers,
Steve