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

From Dilip Kumar
Subject Re: Add sub-transaction overflow status in pg_stat_activity
Date
Msg-id CAFiTN-soxgon4=dy_tOQJKomg8bz=MmuehwAq3zDcxJFvcgm7A@mail.gmail.com
Whole thread Raw
In response to Re: Add sub-transaction overflow status in pg_stat_activity  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Add sub-transaction overflow status in pg_stat_activity  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On Mon, Dec 12, 2022 at 11:21 PM Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Mon, Dec 12, 2022 at 12:42 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
> > index 4efa1d5fca0..ac15e2ce789 100644
> > --- a/doc/src/sgml/monitoring.sgml
> > +++ b/doc/src/sgml/monitoring.sgml
> > @@ -5680,12 +5680,12 @@ FROM pg_stat_get_backend_idset() AS backendid;
> >          <returnvalue>record</returnvalue>
> >         </para>
> >         <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>
> > +        Returns a record of information about the subtransactions of the backend
> > +        with the specified ID.
> > +        The fields returned are <parameter>subxact_count</parameter>, which
> > +        identifies the number of active subtransaction and
> > +        <parameter>subxact_overflow</parameter>, which shows whether the
> > +        backend's subtransaction cache is overflowed or not.
> >         </para></entry>
> >        </row>
>
> Makes sense.

+1

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



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Force streaming every change in logical decoding
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Time delayed LR (WAS Re: logical replication restrictions)