| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Deepak Rai <deepakraib(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-jdbc(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16232: Database server connection limit exceeding |
| Date: | 2020-01-26 16:04:51 |
| Message-ID: | 29778.1580054691@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-jdbc |
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 | Tom Lane | 2020-01-26 16:28:18 | Re: BUG #16233: Yet another "logical replication worker" was terminated by signal 11: Segmentation fault |
| Previous Message | Clemens Eisserer | 2020-01-26 13:07:48 | Re: BUG #16230: Boolean column stick to "false" after calling updateRow() on updateable ResultSet |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Deepak Rai | 2020-01-28 08:43:09 | Re: BUG #16232: Database server connection limit exceeding |
| Previous Message | Clemens Eisserer | 2020-01-26 13:07:48 | Re: BUG #16230: Boolean column stick to "false" after calling updateRow() on updateable ResultSet |