Re: Logical Replication of sequences
Amit Kapila <amit.kapila16@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 Fri, Oct 24, 2025 at 8:52 PM vignesh C <vignesh21@gmail.com> wrote: > > On Thu, 23 Oct 2025 at 16:47, Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Thu, Oct 23, 2025 at 11:45 AM vignesh C <vignesh21@gmail.com> wrote: > > > > > > The attached patch has the changes for the same. > > > > > > > I have pushed 0001 and the following are comments on 0002. > > > > 1. > > @@ -1414,6 +1414,7 @@ CREATE VIEW pg_stat_subscription_stats AS > > ss.subid, > > s.subname, > > ss.apply_error_count, > > + ss.sequence_sync_error_count, > > ss.sync_error_count, > > > > The new parameter name is noticeably longer than other columns. Can we > > name it as ss.seq_sync_error_count. We may also want to reconsider > > changing existing column sync_error_count to tbl_sync_error_count. Can > > we extract this in a separate stats patch? > > Modified and extracted a separate patch for tbl_sync_error_count > Hmm, I didn't want to make the stats related changes before the main patch. I suggested to extract seq_sync_error_count from the main patch and keep it after the main patch. Along with the seq_sync_error_count stats, we can discuss whether to change existing parameter to tbl_sync_error_count. -- With Regards, Amit Kapila.