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

From Petr Jelinek
Subject Re: Logical replication origin tracking fix
Date
Msg-id b623985f-6255-13a6-005b-8af5fa03dba5@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Logical replication origin tracking fix  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
On 10/03/17 05:59, Petr Jelinek wrote:
> Hi,
> 
> 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.

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

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Fix slot name change handling for subscriptions
Next
From: Petr Jelinek
Date:
Subject: Re: logical replication apply to run with sync commit off by default