Re: Synchronizing slots from primary to standby
shveta malik <shveta.malik@gmail.com>
Attachments
- v75-0003-Allow-logical-walsenders-to-wait-for-the-physica.patch (application/octet-stream) patch v75-0003
- v75-0001-libpqrcv-changes-to-support-slot-synchronization.patch (application/octet-stream) patch v75-0001
- v75-0004-Document-the-steps-to-check-if-the-standby-is-re.patch (application/octet-stream) patch v75-0004
- v75-0002-Add-logical-slot-sync-capability-to-the-physical.patch (application/octet-stream) patch v75-0002
On Thu, Feb 1, 2024 at 2:35 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > Agreed, and I am fine with merging 0001, 0002, and 0004 as suggested > by you though I have a few minor comments on 0002 and 0004. I was > thinking about what will be a logical way to split the slot sync > worker patch (combined result of 0001, 0002, and 0004), and one idea > occurred to me is that we can have the first patch as > synchronize_solts() API and the functionality required to implement > that API then the second patch would be a slot sync worker which uses > that API to synchronize slots and does all the required validations. > Any thoughts? If we shift 'synchronize_slots()' to the first patch but there is no caller of it, we may have a compiler warning for the same. The only way it can be done is if we temporarily add SQL function on standby which uses 'synchronize_slots()'. This SQL function can then be removed in later patches where we actually have a caller for 'synchronize_slots'. For the time being, I have merged 1,2, and some parts of 4 into a single patch and separated out libpqrc related changes to the first patch. Attached v75 patch-set. Changes are: 1) Re-arranged the patches: 1.1) 'libpqrc' related changes (from v74-001 and v74-004) are separated out in v75-001 as those are independent changes. 1.2) 'Add logical slot sync capability', 'Slot sync worker as special process' and 'App-name changes' are now merged to single patch which makes v75-002. 1.3) 'Wait for physical Standby confirmation' and 'Failover Validation Document' patches are maintained as is (v75-003 and v75-004 now). 2) Addressed comments by Swada-San, Peter and Amit given in [1], [2], [3] and [4] [1]: https://www.postgresql.org/message-id/CAD21AoDUfnnxP%2By2cg%3DLhP-bQXqFE1z4US-no%3Du30J7X%3D4Z6Aw%40mail.gmail.com [2]: https://www.postgresql.org/message-id/CAD21AoAv6FwZ6UPNTj6%3D7A%2B3O2m4utzfL8ZGS6X1EGexikG66A%40mail.gmail.com [3]: https://www.postgresql.org/message-id/CAHut%2BPuDUT7X7ieB9uQE%3DCLznaVVcQDO2GexkHe1Xfw%3DSWnkPA%40mail.gmail.com [4]: https://www.postgresql.org/message-id/CAA4eK1K7hLU2ZT1VX2k3e21c%3DkOZySZqfVDJsfE9vAS2AZ0mig%40mail.gmail.com thanks Shveta
Commits
-
Doc: Add the new section "Logical Replication Failover".
- b560a98a17ae 17.0 landed
-
Fix the review comments and a bug in the slot sync code.
- 3741f2a09d52 17.0 landed
-
Fix a test in failover slots regression test.
- 7e85d1c75f29 17.0 landed
-
Fix the intermittent buildfarm failures in 040_standby_failover_slots_sync.
- 6f3d8d5e7cc2 17.0 landed
-
Split XLogCtl->LogwrtResult into separate struct members
- c9920a9068ea 17.0 cited
-
Ensure that the sync slots reach a consistent state after promotion without losing data.
- 2ec005b4e297 17.0 landed
-
Introduce a new GUC 'standby_slot_names'.
- bf279ddd1c28 17.0 landed
-
Fix BF failure introduced by commit b3f6b14cf4.
- def0ce337068 17.0 landed
-
Fixups for commit 93db6cbda0.
- b3f6b14cf48f 17.0 landed
-
Fix BF failure in commit 93db6cbda0.
- d13ff82319cc 17.0 landed
-
Add a new slot sync worker to synchronize logical slots.
- 93db6cbda037 17.0 landed
-
Improve ERROR/LOG messages added by commits ddd5f4f54a and 7a424ece48.
- 801792e528d6 17.0 landed
-
Disable autovacuum on primary in 040_standby_failover_slots_sync test.
- b7bdade6a42f 17.0 landed
-
Fix the incorrect format specifier used in commit 7a424ece48.
- b987be39c3c7 17.0 landed
-
Change the LOG level in 040_standby_failover_slots_sync.pl to DEBUG2.
- d9e225f275b7 17.0 landed
-
Add more LOG and DEBUG messages for slot synchronization.
- 7a424ece4828 17.0 landed
-
Another try to fix BF failure introduced in commit ddd5f4f54a.
- 9bc1eee988c3 17.0 landed
-
Fix BF introduced in commit ddd5f4f54a.
- bd8fc1677b88 17.0 landed
-
Add a slot synchronization function.
- ddd5f4f54a02 17.0 landed
-
Clean-ups for 776621a5e4 and 7329240437.
- 22f7e61a6330 17.0 landed
-
Enhance libpqrcv APIs to support slot synchronization.
- dafbfed9efbe 17.0 landed
-
Add a failover option to subscriptions.
- 776621a5e479 17.0 landed
-
Allow setting failover property in the replication command.
- 73292404370c 17.0 landed
-
Allow to enable failover property for replication slots via SQL API.
- c393308b69d2 17.0 landed
-
Add macros for looping through a List without a ListCell.
- 14dd0f27d7cd 17.0 cited
-
Track conflict_reason in pg_replication_slots.
- 007693f2a3ac 17.0 cited
-
Allow upgrades to preserve the full subscription's state.
- 9a17be1e244a 17.0 cited
-
Add support for incremental backup.
- dc212340058b 17.0 cited
-
Simplify some logic in CreateReplicationSlot()
- e83aa9f92fdd 17.0 cited
-
Fix uninitialized access to InitialRunningXacts during decoding after ERROR.
- c7256e6564fa 15.5 cited
-
Flexible options for CREATE_REPLICATION_SLOT.
- 0266e98c6b86 15.0 cited
-
Empty search_path in logical replication apply worker and walsender.
- 11da97024abb 14.0 cited
-
Fix oldest xmin and LSN computation across repslots after advancing
- b48df818dcbd 14.0 cited
-
Require C99 (and thus MSCV 2013 upwards).
- d9dd406fe281 12.0 cited