Re: Add sub-transaction overflow status in pg_stat_activity

Dilip Kumar <dilipbalaut@gmail.com>

From: Dilip Kumar <dilipbalaut@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Amit Singh <amitksingh.mumbai@gmail.com>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Julien Rouhaud <rjuju123@gmail.com>, "Bossart, Nathan" <bossartn@amazon.com>, Ashutosh Sharma <ashu.coek88@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-11-15T05:25:48Z
Lists: pgsql-hackers
On Mon, Nov 14, 2022 at 10:18 PM David G. Johnston
<david.g.johnston@gmail.com> wrote:

>> Do you have a view on this point?
>>
>
> NULL when overflowed seems like the opposite of the desired effect, calling attention to the exceptional status.  Make it a text column and write "overflow" or "###" as appropriate.  Anyone using the column is going to end up wanting to special-case overflow anyway and number-to-text conversion aside from overflow is simple enough if a number, and not just a display label, is needed.

+1, if we are interested to add only one column then this could be the
best way to show.


--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



Commits

  1. Fix comment that was missing a word.

  2. Expose some information about backend subxact status.