Re: Logical replication existing data copy

From: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org
Subject: Re: Logical replication existing data copy
Date: 2017-03-18 12:28:55
Message-ID: 1b7aa90d-0475-714d-3583-f58eebf915ea@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Attachment Content-Type Size
0001-Logical-replication-support-for-initial-data-copy.patch text/x-patch 169.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2017-03-18 12:31:22 Re: logical replication apply to run with sync commit off by default
Previous Message Ashutosh Sharma 2017-03-18 12:00:36 Re: ANALYZE command progress checker