Re: huge SubtransSLRU and SubtransBuffer wait_event
| От | Nikolay Samokhvalov |
|---|---|
| Тема | Re: huge SubtransSLRU and SubtransBuffer wait_event |
| Дата | |
| Msg-id | CANNMO++EdBcR7yHMp4hsYO3NcyKwj_VFy4jzuqA0AGeCfn2XjA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: huge SubtransSLRU and SubtransBuffer wait_event (Laurenz Albe <laurenz.albe@cybertec.at>) |
| Ответы |
Re: huge SubtransSLRU and SubtransBuffer wait_event
RE: huge SubtransSLRU and SubtransBuffer wait_event |
| Список | pgsql-performance |
On Thu, Feb 1, 2024 at 04:42 Laurenz Albe <laurenz.albe@cybertec.at> wrote:
Today, the only feasible solution is not to create more than 64 subtransactions
(savepoints or PL/pgSQL EXCEPTION clauses) per transaction.
Sometimes, a single subtransaction is enough to experience a bad SubtransSLRU spike:
I think 64+ nesting level is quite rare, but this kind of problem that hits you when you have high XID growth (lots of writes) + long-running transaction is quite easy to bump into. Or this case involving MultiXactIDs:
Nik
В списке pgsql-performance по дате отправления: