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

From Petr Jelinek
Subject Re: [HACKERS] Logical replication existing data copy
Date
Msg-id 1b7aa90d-0475-714d-3583-f58eebf915ea@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Logical replication existing data copy  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Logical replication existing data copy  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: [HACKERS] Logical replication existing data copy  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 14/03/17 22:39, Peter Eisentraut wrote:
> On 3/14/17 12:12, Petr Jelinek wrote:
>>> Committing this in chunks makes sense anyway.
>>>
>>> I've attached a slightly version that makes pg_recvlogical skip slot
>>> export. The second patch is unchanged, use the copy from the
>>> immediately prior mail.
>>>
>>
>> Okay, I merged your changes in.
>>
>> Here is that merge, plus the updated main patch that replaces all the
>> SQL interaces in libpqwalreceiver.c with single exec one which uses
>> tuplestore to send any tuple results back.
>>
>> For correct working in every situation, it still needs to snapbuild
>> fixes and also the logical replication origin tracking fix.
> 
> Committed 0001.  Will look at 0002 next.
> 

Cool, rebased the main patch on top of merge conflicts.

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] ANALYZE command progress checker
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] logical replication apply to run with sync commit off by default