Re: repeated decoding of prepared transactions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: repeated decoding of prepared transactions
Date
Msg-id CA+TgmoYt46Ce2Lrfx4GTcUvgx-JQz38b==45cT_f+q4MNO9tKg@mail.gmail.com
Whole thread Raw
In response to Re: repeated decoding of prepared transactions  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tue, Feb 9, 2021 at 9:32 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> If by successfully confirmed, you mean that once the subscriber node
> has received, it won't be sent again then as far as I know that is not
> true. We rely on the flush location sent by the subscriber to advance
> the decoding locations. We update the flush locations after we apply
> the transaction's commit successfully. Also, after the restart, we use
> the replication origin's last flush location as a point from where we
> need the transactions and the origin's progress is updated at commit
> time.
>
> OTOH, If by successfully confirmed, you mean that once the subscriber
> has applied the complete transaction (including commit), then you are
> right that it won't be sent again.

I meant - once the subscriber has advanced the flush location.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: [HACKERS] Custom compression methods
Next
From: Dilip Kumar
Date:
Subject: Re: Is Recovery actually paused?