| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Euler Taveira <euler(at)eulerto(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Subject: | Re: Logical Replication of sequences |
| Date: | 2025-10-28 12:51:04 |
| Message-ID: | CALDaNm1K5y0bL0bGFKC+489RrB8NsCrEOqi+jpPfsDHpWvL6dg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 28 Oct 2025 at 07:17, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
>
>
> > On Oct 27, 2025, at 17:11, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
> >
> > The changes in 0001 are straightforward, looks good. I haven’t reviewed 0004 yet.
>
> Comments for 0004:
>
> 1 - config.sgml
> ```
> - In logical replication, this parameter also limits how often a failing
> - replication apply worker or table synchronization worker will be
> - respawned.
> + In logical replication, this parameter also limits how quickly a
> + failing replication apply worker, table synchronization worker, or
> + sequence synchronization worker will be respawned.
> ```
>
> * “a failing replication apply worker” sounds a bit redundant, maybe change to “a failed apply worker”
> * “will be respawned” works, but in formal documentation, I think “is respawned” is better
I felt this was documented that way in the HEAD too, I prefer the one in HEAD.
> 2 - logic-replication.sgml
> ```
> - or <literal>FOR ALL SEQUENCES</literal>.
> + or <literal>FOR ALL SEQUENCES</literal>. Unlike tables, the current state of
> + sequences may be synchronized at any time. For more information, refer to
> + <xref linkend="logical-replication-sequences"/>.
> ```
>
> * “may be” better to be “can be”
> * I think the first sentence can be slightly enhanced as "Unlike tables, the state of a sequence can be synchronized at any time.”
> * “refer to” should be “see” in PG docs. You can see right the next paragraph just uses “see”:
> ```
> <command>TRUNCATE</command>. See <xref linkend="logical-replication-row-filter"/>).
> ```
Modified
> 3 - logic-replication.sgml
> ```
> + To synchronize sequences from a publisher to a subscriber, first publish
> + them using <link linkend="sql-createpublication-params-for-all-sequences">
> + <command>CREATE PUBLICATION ... FOR ALL SEQUENCES</command></link> and then
> + at the subscriber side:
> ```
>
> “At the subscriber side” is better to be “on the subscriber”. Actually, you also use “on the subscriber” in the following paragraphs.
Modified
> 4 - logic-replication.sgml
> ```
> During sequence synchronization, the sequence definitions of the publisher
> and the subscriber are compared. An ERROR is logged listing all differing
> sequences before the process exits. The apply worker detects this failure
> and repeatedly respawns the sequence synchronization worker to continue
> the synchronization process until all differences are resolved. See also
> ```
>
> * “An ERROR” => “An error”. If you search for the current doc, “error” are all in lower case.
> * " the sequence synchronization worker to continue the synchronization process”, the second “synchronization” sounds redundant, maybe enhance to "the sequence synchronization worker to retry"
Modified
> 5 - logic-replication.sgml
> ```
> During sequence synchronization, if a sequence is dropped on the
> publisher, the sequence synchronization worker will identify this and
> remove it from sequence synchronization on the subscriber.
> ```
>
> “Will identify this” => “detects the change”, I think PG docs usually prefer more direct phrasing.
This behavior has been changed now, I have removed it.
These changes are available in the v20251029 version posted at [1].
[1] - https://www.postgresql.org/message-id/CAHut%2BPtMc1fr6cQvUAnxRE%2Bbuim5m-d9M2dM0YAeEHNkS9KzBw%40mail.gmail.com
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | BharatDB | 2025-10-28 12:51:41 | Re: Checkpointer write combining |
| Previous Message | Rahila Syed | 2025-10-28 12:41:25 | Extend injection_points_attach() to accept a user-defined function |