Re: Synchronizing slots from primary to standby
shveta malik <shveta.malik@gmail.com>
Attachments
- scripts.zip (application/x-zip-compressed)
On Mon, Aug 14, 2023 at 3:22 PM shveta malik <shveta.malik@gmail.com> wrote: > > On Tue, Aug 8, 2023 at 11:11 AM Drouvot, Bertrand > <bertranddrouvot.pg@gmail.com> wrote: > > > > Hi, > > > > On 8/8/23 7:01 AM, shveta malik wrote: > > > On Mon, Aug 7, 2023 at 3:17 PM Drouvot, Bertrand > > > <bertranddrouvot.pg@gmail.com> wrote: > > >> > > >> Hi, > > >> > > >> On 8/4/23 1:32 PM, shveta malik wrote: > > >>> On Fri, Aug 4, 2023 at 2:44 PM Drouvot, Bertrand > > >>> <bertranddrouvot.pg@gmail.com> wrote: > > >>>> On 7/28/23 4:39 PM, Bharath Rupireddy wrote: > > >> > > > > > > Agreed. That is why in v10,v11 patches, we have different infra for > > > sync-slot worker i.e. it is not relying on "logical replication > > > background worker" anymore. > > > > yeah saw that, looks like the right way to go to me. > > > > >> Maybe we should start some tests/benchmark with only one sync worker to get numbers > > >> and start from there? > > > > > > Yes, we can do that performance testing to figure out the difference > > > between the two modes. I will try to get some statistics on this. > > > > > > > Great, thanks! > > > > We (myself and Ajin) performed the tests to compute the lag in standby > slots as compared to primary slots with different number of slot-sync > workers configured. > > 3 DBs were created, each with 30 tables and each table having one > logical-pub/sub configured. So this made a total of 90 logical > replication slots to be synced. Then the workload was run for aprox 10 > mins. During this workload, at regular intervals, primary and standby > slots' lsns were captured (from pg_replication_slots) and compared. At > each capture, the intent was to know how much is each standby's slot > lagging behind corresponding primary's slot by taking the distance > between confirmed_flush_lsn of primary and standby slot. Then we took > the average (integer value) of this distance over the span of 10 min > workload and this is what we got: > I have attached the scripts for schema-setup, running workload and capturing lag. Please go through Readme for details. 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