Re: BUG #18141: sorry, too many clients error occurring very frequently
От | Joe Conway |
---|---|
Тема | Re: BUG #18141: sorry, too many clients error occurring very frequently |
Дата | |
Msg-id | b3d50783-fc7d-0239-5343-6bfe7f654334@joeconway.com обсуждение исходный текст |
Ответ на | Re: BUG #18141: sorry, too many clients error occurring very frequently (Jeff Janes <jeff.janes@gmail.com>) |
Ответы |
Re: BUG #18141: sorry, too many clients error occurring very frequently
|
Список | pgsql-bugs |
On 9/30/23 14:04, Jeff Janes wrote: > On Fri, Sep 29, 2023 at 7:55 PM PG Bug reporting form > <noreply@postgresql.org <mailto:noreply@postgresql.org>> wrote: > > The following bug has been logged on the website: > > Bug reference: 18141 > Logged by: Ravi Agrawal > Email address: ravi.s.agrawal23@gmail.com > <mailto:ravi.s.agrawal23@gmail.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? Maybe, maybe not. I have seen two other cases that are similar. One was an upgrade from 12.8 to 12.12 and the other an upgrade from 13.4 to 13.8. I checked and 12.8 was stamped is the same date as 13.4, and 12.12 the same day as 13.8. In both cases queries against pg_stat_statements suddenly started taking more memory leading to spillage to pg_temp and a step degradation in overall performance. In at least one of those cases the solution/workaround was to increase work_mem. In the other I think pg_stat_statements was disabled. Myself and at least one other hacker looked at the pg_stat_statements specific changes in that time interval and saw no smoking gun. But it is possible that something else backpatched to both branches between Aug 09, 2021 and Aug 8, 2022 has caused a more general performance regression which we have yet to track down. At least based on this sample of two (now maybe 3?) folks with similar symptoms. -- Joe Conway PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-bugs по дате отправления: