Re: Logical replication origin tracking fix - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Logical replication origin tracking fix
Date
Msg-id 69ff9da5-0ebc-cadd-c405-997349370b51@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Logical replication origin tracking fix  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
On 3/24/17 10:48, Petr Jelinek wrote:
> On 10/03/17 05:59, Petr Jelinek wrote:
>> while discussing with Craig issues around restarting logical replication
>> stream related to the patch he posted [1], I realized that we track
>> wrong origin LSN in the logical replication apply.
>>
>> We currently track commit_lsn which is *start* of commit record, what we
>> need to track is end_lsn which is *end* of commit record otherwise we
>> might request transaction that was already replayed if the subscription
>> instance has crashed right after commit.
>>
>> Attached patch fixes that.
>>
> 
> Rebase after table copy patch got committed.

committed

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Rewriting the test of pg_upgrade as a TAP test
Next
From: Peter Eisentraut
Date:
Subject: Re: Logical replication SnapBuildInitalSnapshot spelling