| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Small doc improvement about spilled txn tracking |
| Date: | 2020-06-02 04:52:26 |
| Message-ID: | CAA4eK1KdotGWFh8=RRnnt2DSx_FNXT+a3q1sCuPqQTyEoCUCrg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 2, 2020 at 9:10 AM Masahiko Sawada
<masahiko(dot)sawada(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-06-02 05:01:02 | Re: Read access for pg_monitor to pg_replication_origin_status view |
| Previous Message | Michael Paquier | 2020-06-02 04:49:17 | Re: Read access for pg_monitor to pg_replication_origin_status view |