RE: huge SubtransSLRU and SubtransBuffer wait_event
От | James Pang (chaolpan) |
---|---|
Тема | RE: huge SubtransSLRU and SubtransBuffer wait_event |
Дата | |
Msg-id | PH0PR11MB51911DC56A32BE96ED11D63BD6432@PH0PR11MB5191.namprd11.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: huge SubtransSLRU and SubtransBuffer wait_event (Laurenz Albe <laurenz.albe@cybertec.at>) |
Ответы |
RE: huge SubtransSLRU and SubtransBuffer wait_event
|
Список | pgsql-performance |
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. You mean extensions to simulate a subtransaction like pg_background ? for JDBC driver option to simulate statement levelrollback, could you share more details ? Thanks, James -----Original Message----- From: Laurenz Albe <laurenz.albe@cybertec.at> Sent: Thursday, February 1, 2024 8:42 PM To: James Pang (chaolpan) <chaolpan@cisco.com>; pgsql-performance@lists.postgresql.org Subject: Re: huge SubtransSLRU and SubtransBuffer wait_event 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
В списке pgsql-performance по дате отправления: