From: | Deepak Rai <deepakraib(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-jdbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16232: Database server connection limit exceeding |
Date: | 2020-01-28 08:43:09 |
Message-ID: | CABiotD2Lj_Pbu6WCOJ2J8QeeB-Gi+pqgGWKdEDyfGux93sepbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-jdbc |
Hi Team,
Any update on this?
Regards,
Deepak
On Sun, Jan 26, 2020 at 9:36 PM Deepak Rai <deepakraib(at)gmail(dot)com> wrote:
> Hi Tom,
>
> Super user reserved is 3, it was default value and we have not done any
> changes.
>
> Regards,
> Deepak
>
> On Sun, 26 Jan, 2020, 9:34 pm Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Deepak Rai <deepakraib(at)gmail(dot)com> writes:
>> > We are actively monitoring database connections and total connection
>> count
>> > was not more than 14. Max connections are allowed in the database is
>> 300.
>> > May i know why this is occurring even though connection is not crossing
>> its
>> > threshold.
>>
>> Over-aggressive setting for superuser_reserved_connections, perhaps?
>> Another possibility is a whole lot of uncommitted prepared transactions.
>>
>> regards, tom lane
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Johann du Toit | 2020-01-28 09:34:15 | Re: BUG #16233: Yet another "logical replication worker" was terminated by signal 11: Segmentation fault |
Previous Message | Tom Lane | 2020-01-27 23:05:45 | Re: BUG #16236: Invalid escape encoding |
From | Date | Subject | |
---|---|---|---|
Next Message | Svein Baardsen | 2020-01-28 15:54:22 | [pgjdbc/pgjdbc] e38868: fix: #1677 NumberFormatException when fetching PGI... |
Previous Message | Tom Lane | 2020-01-26 16:04:51 | Re: BUG #16232: Database server connection limit exceeding |