BUG #16232: Database server connection limit exceeding

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: deepakraib(at)gmail(dot)com
Subject: BUG #16232: Database server connection limit exceeding
Date: 2020-01-26 03:39:49
Message-ID: 16232-26f076ca50acb16d@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs pgsql-jdbc

The following bug has been logged on the website:

Bug reference: 16232
Logged by: DEEPAK RAI B
Email address: deepakraib(at)gmail(dot)com
PostgreSQL version: 9.6.9
Operating system: Core OS

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",,,,,,,,,""


Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-01-26 06:46:00 BUG #16233: Yet another "logical replication worker" was terminated by signal 11: Segmentation fault
Previous Message Eduardo Lúcio Amorim Costa 2020-01-26 00:31:44 Re: SQL/PostgreSQL - Error observed in the QUERY not caught by the “EXCEPTION” block in the stored procedure

Browse pgsql-jdbc by date

  From Date Subject
Next Message David G. Johnston 2020-01-26 06:47:52 Re: BUG #16232: Database server connection limit exceeding
Previous Message Clemens Eisserer 2020-01-25 19:07:53 Re: Boolean column stick to "false" after calling updateRow() on updateable ResultSet