Re: Add sub-transaction overflow status in pg_stat_activity
От | Bossart, Nathan |
---|---|
Тема | Re: Add sub-transaction overflow status in pg_stat_activity |
Дата | |
Msg-id | C21036F3-CA22-4CA4-AA9F-099C75F082FC@amazon.com обсуждение исходный текст |
Ответ на | Re: Add sub-transaction overflow status in pg_stat_activity (Dilip Kumar <dilipbalaut@gmail.com>) |
Ответы |
Re: Add sub-transaction overflow status in pg_stat_activity
|
Список | pgsql-hackers |
On 12/13/21, 6:30 AM, "Dilip Kumar" <dilipbalaut@gmail.com> wrote: > On Tue, Dec 7, 2021 at 11:11 AM Justin Pryzby <pryzby@telsasoft.com> wrote: >> Since I think this field is usually not interesting to most users of >> pg_stat_activity, maybe this should instead be implemented as a function like >> pg_backend_get_subxact_status(pid). >> >> People who want to could use it like: >> SELECT * FROM pg_stat_activity psa, pg_backend_get_subxact_status(pid) sub; > > I have provided two function, one for subtransaction counts and other > whether subtransaction cache is overflowed or not, we can use like > this, if we think this is better way to do it then we can also add > another function for the lastOverflowedXid The general approach looks good to me. I think we could have just one function for all three values, though. Nathan
В списке pgsql-hackers по дате отправления: