> Test-scenario: > --Created 250 sequences on both pub and sub. > --There were 10 sequences mismatched. > --Sequence replication worked as expected. Logs look better now: > > LOG: Logical replication sequence synchronization for subscription > "sub1" - total unsynchronized: 250; batch #1 = 100 attempted, 97 > succeeded, 3 mismatched > LOG: Logical replication sequence synchronization for subscription > "sub1" - total unsynchronized: 250; batch #2 = 100 attempted, 95 > succeeded, 5 mismatched > LOG: Logical replication sequence synchronization for subscription > "sub1" - total unsynchronized: 250; batch #3 = 50 attempted, 48 > succeeded, 2 mismatched >
When there are many batches required, it seems a bit strange to repeat the same "total unsynchronized" over and over. Would it be better to show the total number once, and thereafter show the number of sequences remaining to be processed as they tick down? e.g. LOG: Logical replication sequence synchronization for subscription "sub1" - total unsynchronized = 250 LOG: Logical replication sequence synchronization for subscription "sub1" - batch #1 = 100 attempted, 97 succeeded, 3 mismatched, 150 remaining LOG: Logical replication sequence synchronization for subscription "sub1" - batch #2 = 100 attempted, 95 succeeded, 5 mismatched, 50 remaining LOG: Logical replication sequence synchronization for subscription "sub1" - batch #3 = 50 attempted, 48 succeeded, 2 mismatched, 0 remaining ====== Kind Regards, Peter Smith. Fujitsu Australia
