Re: Logical Replication of sequences
Dilip Kumar <dilipbalaut@gmail.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: Add documentation for sequence synchronization.
- 55cefadde874 19 (unreleased) landed
-
Remove unused assignment in CREATE PUBLICATION grammar.
- bfb7419b0bbe 19 (unreleased) landed
-
Add seq_sync_error_count to subscription statistics.
- f6a4c498dcf6 19 (unreleased) landed
-
Fix few issues in commit 5509055d69.
- 5a4eba558aa7 19 (unreleased) landed
-
Add sequence synchronization for logical replication.
- 5509055d6956 19 (unreleased) landed
-
Add worker type argument to logical replication worker functions.
- 3e8e05596a02 19 (unreleased) landed
-
Introduce "REFRESH SEQUENCES" for subscriptions.
- f0b3573c3aac 19 (unreleased) landed
-
Refactor logical worker synchronization code into a separate file.
- 41c674d2e31e 19 (unreleased) landed
-
Standardize use of REFRESH PUBLICATION in code and messages.
- 2436b8c047ff 19 (unreleased) landed
-
Add "ALL SEQUENCES" support to publications.
- 96b378497346 19 (unreleased) landed
-
Expose sequence page LSN via pg_get_sequence_data.
- b93172ca59f4 19 (unreleased) landed
-
Resume conflict-relevant data retention automatically.
- 0d48d393d465 19 (unreleased) cited
-
Post-commit review fixes for 228c370868.
- 1f7e9ba3ac4e 19 (unreleased) cited
-
Generate GUC tables from .dat file
- 63599896545c 19 (unreleased) cited
On Thu, Oct 9, 2025 at 12:30 PM Peter Smith <smithpb2250@gmail.com> wrote: > > I think the "ALTER SUBSCRIPTION sub REFRESH PUBLICATION" command has > the word PUBLICATION in it because it's the PUBLICATION has changed > (stuff added/removed), so we need to refresh it. > > OTOH, the synchronisation of *existing* sequences is different - this > is more like the subscription saying "Just get me updated values for > the sequences I already know about". Therefore, I don't think the word > PUBLICATION is relevant here. > > ~~ > > So my suggestion is very different. Just this: > "ALTER SUBSCRIPTION sub REFRESH SEQUENCES" > > I feel this is entirely consistent, because: > > PUBLICATION objects have changed. Refresh me the new objects => ALTER > SUBSCRIPTION sub REFRESH PUBLICATION; > > SEQUENCE values have changed. Refresh me the new values => ALTER > SUBSCRIPTION sub REFRESH SEQUENCES; I prefer this suggestion over the previous proposal so +1 from my side. -- Regards, Dilip Kumar Google