| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, "Maksim(dot)Melnikov" <m(dot)melnikov(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Init connection time grows quadratically |
| Date: | 2026-09-18 01:54:54 |
| Message-ID: | CAGRkXqQkYa6Onb0HAvFbJmpwokXug6=ECk2YByCeNmEsumZo4A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
As CF manager, I moved this entry from Ready for Committer to Waiting on
Author.
> Maybe I am just missing something, but is this ever a benefit outside of
> completely arbitrary scenarios?
On Andres's question, the closest workload I have seen is an AI app
behind pgbouncer. Some transactions stay open while they wait for an LLM
response, and background loading causes transactionid and tuple lock
waits. In spikes, pgbouncer grew to about 4000 server connections, then
shrank again.
The real problem there is locks and long transactions. This patch might help
the connection storm, but may not fix it.
In addition, CFBot now tests v6, not v5. Haibo, please post v6 separately.
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-09-18 01:59:57 | Re: pg_xmin_horizon: a system view of everything pinning the xmin horizon |
| Previous Message | Hayato Kuroda (Fujitsu) | 2026-09-18 01:49:34 | RE: pgoutput: schema cache cleanup after streamed 2PC |