On Tue, 20 Dec 2022 at 09:23, Dilip Kumar <dilipbal...@gmail.com> wrote: > > On Tue, Dec 20, 2022 at 2:32 AM Robert Haas <robertmh...@gmail.com> wrote: > > > > On Mon, Dec 19, 2022 at 3:48 PM Ted Yu <yuzhih...@gmail.com> wrote: > > > It seems the comment for `backend_subxact_overflowed` missed a word. > > > > > > Please see the patch. > > > > Committed this fix, thanks. > > Thanks, Robert! > > -- > Regards, > Dilip Kumar > EnterpriseDB: http://www.enterprisedb.com > >
Hi hackers! Nice patch, seems it may be useful in cases like alerting that subxid overflow happened is database or whatever. But I'm curious, what is the following work on this? I think it may be way more helpful to, for example, log queries, causing sub-tx overflow, or even kill the backend, causing sub-tx overflow with GUC variables, setting server behaviour. For example, in Greenplum there is gp_subtransaction_overflow extension and GUC for simply logging problematic queries[1]. Can we have something similar in PostgreSQL on the server-side? [1] https://github.com/greenplum-db/gpdb/blob/6X_STABLE/gpcontrib/gp_subtransaction_overflow/gp_subtransaction_overflow.c#L42
