From: | Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta(dot)malik(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: DOCS - pg_replication_slot . Fix the 'inactive_since' description |
Date: | 2024-11-14 06:42:33 |
Message-ID: | CABdArM7652askN5-xX5xrvPBwBJCm4q9sRjL_kna5i2qWdeLGQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 31, 2024 at 11:05 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>
> Yes, all good suggestions, updated patch attached.
>
Few comments for the changes under "inactive_since" description:
+ The time when slot synchronization (see <xref
+ linkend="logicaldecoding-replication-slots-synchronization"/>)
+ was most recently stopped. <literal>NULL</literal> if the slot
+ has always been synchronized. This is useful for slots on the
+ standby that are being synced from a primary server (whose
+ <structfield>synced</structfield> field is <literal>true</literal>)
+ so they know when the slot stopped being synchronized.
1)
To me, the above lines give the impression that "inactive_since" is
only meaningful for the logical slots which are being synchronized
from primary to standby, which is not correct. On a primary node, this
column gives the timestamp when any slot becomes inactive. By removing
the line -
- The time since the slot has become inactive.
I feel we lost the description that explains this column’s purpose on
primary nodes. I suggest explicitly clarifying the inactive_since
column's meaning on primary nodes as well.
2) Can we add more details to it for column's behavior on restarting
a node, something like -
"For the inactive slots, restarting a node resets the "inactive_since"
time to the node's start time. "
--
Thanks,
Nisha
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2024-11-14 06:52:44 | Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY |
Previous Message | Michael Paquier | 2024-11-14 06:34:11 | Re: logical replication: restart_lsn can go backwards (and more), seems broken since 9.4 |