Re: Logical replication existing data copy - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: Logical replication existing data copy
Date
Msg-id 9614f59cbb938b65dfa22c292eea4f85@xs4all.nl
Whole thread Raw
In response to [HACKERS] Logical replication existing data copy  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
(At the moment using these patches for tests:) 0001-Reserve-global-xmin-for-create-slot-snasphot-export.patch +
0002-Don-t-use-on-disk-snapshots-for-snapshot-export-in-l.patch+
0003-Prevent-snapshot-builder-xmin-from-going-backwards.patch +
0004-Fix-xl_running_xacts-usage-in-snapshot-builder.patch     + 0005-Skip-unnecessary-snapshot-builds.patch
      + and now (Tuesday 30) added : 0001-Fix-remote-position-tracking-in-logical-replication.patch
 


> I think what you have seen is because of this:
>
https://www.postgresql.org/message-id/flat/b235fa69-147a-5e09-f8f3-3f780a1abb2e@2ndquadrant.com#b235fa69-147a-5e09-f8f3-3f780a1abb2e@2ndquadrant.com
> 

You were right: with that 6th patch (and wal_sender_timout back at its 
default 60s) there are no errors either (I tested on all 3 
test-machines).

I must have missed that last patch when you posted it.  Anyway all seems 
fine now; I hope the above patches can all be committed soon.

thanks,

Erik Rijkers




pgsql-hackers by date:

Previous
From: Kuntal Ghosh
Date:
Subject: Re: strange parallel query behavior after OOM crashes
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCH] few fts functions for jsonb