| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: huge SubtransSLRU and SubtransBuffer wait_event |
| Date: | 2024-02-01 12:41:53 |
| Message-ID: | 2e9c28409b28546235c68e6440e6f9e9cf4be995.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 2024-02-01 at 11:50 +0000, James Pang (chaolpan) wrote:
> We have a Postgresqlv14.8 server, client use Postgresql JDBC connections, today,
> our server see a lot of “SubtransBuffer” and “SubtransSLRU” wait_event.
> Could you help direct me what’s the possible cause and how to resolve this waits ?
Today, the only feasible solution is not to create more than 64 subtransactions
(savepoints or PL/pgSQL EXCEPTION clauses) per transaction.
Don't use extensions or the JDBC driver option to simulate statement level rollback,
that is the road to hell.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Blanch Bataller | 2024-02-01 13:40:20 | Memory growth using many named prepared statements, in spite of using DISCARD ALL afterwards. |
| Previous Message | James Pang (chaolpan) | 2024-02-01 11:50:57 | huge SubtransSLRU and SubtransBuffer wait_event |