Re: Add sub-transaction overflow status in pg_stat_activity

From: Zhihong Yu <zyu(at)yugabyte(dot)com>
To: Dilip Kumar <dilipbalaut(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 04:30:29
Message-ID: CALNJ-vTcuBoHMdRcURc8AqpyvAtJhOu0LgpehLHdri2EeL1bUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 6, 2021 at 8:17 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]
>
> [1]
> https://www.postgresql.org/message-id/CAFiTN-t5BkwdHm1bV8ez64guWZJB_Jjhb7arsQsftxEwpYwObg%40mail.gmail.com
>
>
> --
> Regards,
> Dilip Kumar
> EnterpriseDB: http://www.enterprisedb.com

Hi,

bq. there is a no way to

Extra 'a' before no.

+ * Number of active subtransaction in the current session.

subtransaction -> subtransactions

+ * Whether subxid count overflowed in the current session.

It seems 'count' can be dropped from the sentence.

Cheers

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Samokhvalov 2021-12-07 04:59:12 Re: Add sub-transaction overflow status in pg_stat_activity
Previous Message Dilip Kumar 2021-12-07 04:16:25 Add sub-transaction overflow status in pg_stat_activity