Re: Logical Replication of sequences
vignesh C <vignesh21@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
Attachments
- v20240807-0001-Introduce-pg_sequence_state-function-for-e.patch (text/x-patch) patch v20240807-0001
- v20240807-0002-Introduce-ALL-SEQUENCES-support-for-Postgr.patch (text/x-patch) patch v20240807-0002
- v20240807-0003-Enhance-sequence-synchronization-during-su.patch (text/x-patch) patch v20240807-0003
On Tue, 6 Aug 2024 at 14:38, Peter Smith <smithpb2250@gmail.com> wrote: > > Here are some review comments for the patch v20240805_2-0003. > > 4a. > Is there a way to give more helpful information by identifying what > was different in the log? OTOH, maybe it would become too messy if > there were multiple differences... I had considered this while implementing and did not implement it to print each of the parameters because it will be too messy. I felt existing is better. > > 7. More test cases? > IIUC you can also get a sequence mismatch warning during "ALTER ... > REFRESH PUBLICATION", and "CREATE SUBSCRIPTION". So, should those be > tested also? Since it won't add any extra coverage, I feel no need to add this test. The remaining comments have been addressed, and the changes are included in the attached v20240807 version patch. Regards, Vignesh