Re: Max connections reached without max connections reached
От | Amul Sul |
---|---|
Тема | Re: Max connections reached without max connections reached |
Дата | |
Msg-id | CAAJ_b94czoEydNS9DP74AHus7TaCV2SU-VqOp+vm_FkRpfowLg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Max connections reached without max connections reached (James Sewell <james.sewell@jirotech.com>) |
Ответы |
Re: Max connections reached without max connections reached
|
Список | pgsql-general |
On Mon, Dec 6, 2021 at 6:11 AM James Sewell <james.sewell@jirotech.com> wrote: >> >> Agreed with both points. What about we add, subxid count and overflow >> status in LocalPgBackendStatus and through that, we can show in >> pg_stat_activity. That way we don't have to report it ever and >> whenever the user is running pg_stat_activity they can fetch it >> directly from "proc->subxidStatus", along with fetching the proc.xid >> and proc.xmin. Does this make sense? > > > Not sure about the overhead and performance aspects, but I like this solution from a functional point of view. > +1, I too like the idea. The patch doesn't seem to be doing any heavy lifting, I think that much overhead should be acceptable. Regards, Amul
В списке pgsql-general по дате отправления: