Re: Add sub-transaction overflow status in pg_stat_activity

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add sub-transaction overflow status in pg_stat_activity
Date: 2021-12-07 17:24:36
Message-ID: 82E46491-91DA-491D-9D85-189F098EBAE5@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/6/21, 8:19 PM, "Dilip Kumar" <dilipbalaut(at)gmail(dot)com> wrote:
> If the subtransaction cache is overflowed in some of the transactions
> then it will affect all the concurrent queries as they need to access
> the SLRU for checking the visibility of each tuple. But currently
> there is no way to identify whether in any backend subtransaction is
> overflowed or what is the current active subtransaction count.
> Attached patch adds subtransaction count and subtransaction overflow
> status in pg_stat_activity. I have implemented this because of the
> recent complain about the same[1]

I'd like to give a general +1 to this effort. Thanks for doing this!
I've actually created a function to provide this information in the
past, so I will help review.

Nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-12-07 17:30:48 Re: ExecTypeSetColNames is fundamentally broken
Previous Message Tom Lane 2021-12-07 17:19:41 Re: Dubious usage of TYPCATEGORY_STRING