From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | ravi(dot)s(dot)agrawal23(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18141: sorry, too many clients error occurring very frequently |
Date: | 2023-09-30 18:04:56 |
Message-ID: | CAMkU=1zXTm-zAq2jRoscmqDmDGPjRy_18BhOn_-Jb0TuGbHHbg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Sep 29, 2023 at 7:55 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18141
> Logged by: Ravi Agrawal
> Email address: ravi(dot)s(dot)agrawal23(at)gmail(dot)com
> PostgreSQL version: 13.11
> Operating system: RHEL
> Description:
>
> Hi Team,
>
> We have updated PostgresSQL from version 13.4 to 13.11 and observing
> 'sorry,
> too many clients' error very frequently.
> Connection count is shooting up on performing basic operations and
> crossing
> the max_connections value. This has not been observed previously on
> Postgres
> v13.4
> We need to understand if this issue is caused due to the change in version.
> Is there any history of known incidents facing this issue with the specific
> version of PostgreSQL.
>
I think it is unlikely to be a bug. How did you do the upgrade? Just
install the new binaries, then restart the server?
Can you capture plans from the newly slow queries and compare them to plans
from the same queries before the upgrade?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-09-30 23:48:10 | Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned |
Previous Message | Jorge Soro Domenech | 2023-09-30 10:33:38 | Help pg_restore version |