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

From Robert Haas
Subject Re: repeated decoding of prepared transactions
Date
Msg-id CA+TgmoYvg6GL15uOg3fGTvwKcNGE5q+KhtAERFcdXup_axk+Mg@mail.gmail.com
Whole thread Raw
In response to Re: repeated decoding of prepared transactions  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: repeated decoding of prepared transactions
List pgsql-hackers
On Tue, Feb 9, 2021 at 6:57 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> I think similar happens without any of the work done in PG-14 as well
> if we restart the apply worker before the commit completes on the
> subscriber. After the restart, we will send the start_decoding_at
> point based on some previous commit which will make publisher send the
> entire transaction again. I don't think restart of WAL sender or WAL
> receiver is such a common thing. It can only happen due to some bug in
> code or user wishes to stop the nodes or some crash happened.

Really? My impression is that the logical replication protocol is
supposed to be designed in such a way that once a transaction is
successfully confirmed, it won't be sent again. Now if something is
not confirmed then it has to be sent again. But if it is confirmed
then it shouldn't happen.

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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Perform COPY FROM encoding conversions in larger chunks
Next
From: Pavel Borisov
Date:
Subject: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.