Re: Small doc improvement about spilled txn tracking - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Small doc improvement about spilled txn tracking
Date
Msg-id CAA4eK1KdotGWFh8=RRnnt2DSx_FNXT+a3q1sCuPqQTyEoCUCrg@mail.gmail.com
Whole thread Raw
In response to Small doc improvement about spilled txn tracking  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Responses Re: Small doc improvement about spilled txn tracking  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tue, Jun 2, 2020 at 9:10 AM Masahiko Sawada
<masahiko.sawada@2ndquadrant.com> wrote:
>
> Hi all,
>
> When reading pg_stat_replication doc of PG13, I thought it's better to
> mention that tracking of spilled transactions works only for logical
> replication like we already mentioned about replication lag tracking:
>
>   <para>
>    Lag times work automatically for physical replication. Logical decoding
>    plugins may optionally emit tracking messages; if they do not, the tracking
>    mechanism will simply display NULL lag.
>   </para>
>
> What do you think?
>

+1.

> Please find attached patch.
>

On a quick look, it seems fine but I will look in more detail and let
you know if I have any feedback.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Read access for pg_monitor to pg_replication_origin_status view
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Read access for pg_monitor to pg_replication_origin_status view