Re: BUG #16232: Database server connection limit exceeding

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: deepakraib(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16232: Database server connection limit exceeding
Date: 2020-01-26 06:47:52
Message-ID: CAKFQuwYL-b=xQ2vAU0+t0yzrpuQAtBJ3kLSOffYK42+1HiCztg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-jdbc

On Sat, Jan 25, 2020 at 8:40 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

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

Not likely to be a bug. The issue is you've hit the max connections
allowed for non-superuser connections. You can inspect log files (possibly
after changing log settings) or plug in some active poll-based monitoring
to discover exactly how that is happening.

Follow-on questions or help is more appropriately directed to the -general
email list and not the bug reporting forum.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2020-01-26 06:53:58 Re: SQL/PostgreSQL - Error observed in the QUERY not caught by the “EXCEPTION” block in the stored procedure
Previous 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

Browse pgsql-jdbc by date

  From Date Subject
Next Message David G. Johnston 2020-01-26 06:56:53 Re: BUG #16230: Boolean column stick to "false" after calling updateRow() on updateable ResultSet
Previous Message PG Bug reporting form 2020-01-26 03:39:49 BUG #16232: Database server connection limit exceeding