From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: deepakraib@gmail.com
Subject: BUG #16231: Database server connection limit exceeding
Date: Sun, 26 Jan 2020 03:39:49 +0000
Message-ID: <16231-2dd46ad821fbc40d@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16231
Logged by: DEEPAK RAI B
Email address: deepakraib@gmail.com
PostgreSQL version: 9.6.9
Operating system: Core OS
Description:
Hi Team,
We are getting below error even though total connection in the database
(select count(*) from pg_stat_activity;) is not more than 10 and
max_connections are allowed 300. We are seeing below error most of the time
and only sometime it is impacting our application. Please let me know what
might be the issue?
"startup",2020-01-23 15:17:25 UTC,1999/7,0,FATAL,53300,"remaining connection
slots are reserved for non-replication superuser connections",,,,,,,,,""
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, deepakraib@gmail.com
Subject: Re: BUG #16231: Database server connection limit exceeding
In-Reply-To: <16231-2dd46ad821fbc40d@postgresql.org>
References: <16231-2dd46ad821fbc40d@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox