Re: Include sequences in publications created by pg_createsubscriber
Peter Smith <smithpb2250@gmail.com>
From: Peter Smith <smithpb2250@gmail.com>
To: Ashutosh Sharma <ashu.coek88@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-25T05:57:46Z
Lists: pgsql-hackers
On Thu, Jun 25, 2026 at 5:35 PM Ashutosh Sharma <ashu.coek88@gmail.com> wrote: > > Hi, > > On Thu, Jun 25, 2026 at 6:29 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > 3. > > <para> > > Enable the subscription for each specified database on the target server. > > The subscription starts applying transactions from the replication start > > - point. > > + point. The subscription is configured to include sequences. > > </para> > > > > This implies there was some special subscription "configuration" for > > getting sequences, but it just gets sequences because sequences were > > published. Maybe you don't need to say anything here. Or, maybe reword > > to just say "The subscription will include sequences". > > > > What if the subscription uses an existing publication that doesn't > include sequences? In that case, would it be correct to say that the > subscription will include sequences? > Oops. Fair point. Looks like the original patch text suffered similar issues. A more descriptive explanation seems needed for this to talk about the differences of internal publications versus user-supplied ones.... e.g. a user-publication may even be only FOR ALL SEQUENCES and not even have tables in them... then what? ====== Kind Regards, Peter Smith. Fujitsu Australia.
Commits
-
Add sequence synchronization for logical replication.
- 5509055d6956 19 (unreleased) cited
-
Add "ALL SEQUENCES" support to publications.
- 96b378497346 19 (unreleased) cited