Add sub-transaction overflow status in pg_stat_activity - Mailing list pgsql-hackers

From Dilip Kumar
Subject Add sub-transaction overflow status in pg_stat_activity
Date
Msg-id CAFiTN-uvYAofNRaGF4R+u6_OrABdkqNRoX7V6+PP3H_0HuYMwg@mail.gmail.com
Whole thread Raw
Responses Re: Add sub-transaction overflow status in pg_stat_activity  (Zhihong Yu <zyu@yugabyte.com>)
Re: Add sub-transaction overflow status in pg_stat_activity  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
Re: Add sub-transaction overflow status in pg_stat_activity  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: pg_get_publication_tables() output duplicate relid
Next
From: Zhihong Yu
Date:
Subject: Re: Add sub-transaction overflow status in pg_stat_activity