| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add sub-transaction overflow status in pg_stat_activity |
| Date: | 2022-01-13 22:27:31 |
| Message-ID: | 1B794E40-5217-4793-920A-0565037068AC@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks for the new patch!
+ <para>
+ Returns a record of information about the backend's subtransactions.
+ The fields returned are <parameter>subxact_count</parameter> identifies
+ number of active subtransaction and <parameter>subxact_overflow
+ </parameter> shows whether the backend's subtransaction cache is
+ overflowed or not.
+ </para></entry>
+ </para></entry>
nitpick: There is an extra "</para></entry>" here.
Would it be more accurate to say that subxact_count is the number of
subxids that are cached? It can only ever go up to
PGPROC_MAX_CACHED_SUBXIDS.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petar Dambovaliev | 2022-01-13 23:02:57 | Undocumented error |
| Previous Message | Bossart, Nathan | 2022-01-13 22:04:11 | Re: do only critical work during single-user vacuum? |