Re: [BUG]Update Toast data failure in logical replication - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [BUG]Update Toast data failure in logical replication
Date
Msg-id CA+TgmoY9g58mvnnHT4a4vNVVd=dK6wXQAew21y06s1xqTzEcRw@mail.gmail.com
Whole thread Raw
In response to Re: [BUG]Update Toast data failure in logical replication  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Jan 24, 2022 at 4:42 PM Andres Freund <andres@anarazel.de> wrote:
> On 2022-01-24 16:31:08 -0500, Robert Haas wrote:
> > That seems consistent with what's been described on this thread so
> > far, but I still don't quite understand why the logic that reassembles
> > TOAST chunks doesn't solve it.
>
> There are no toast chunks to reassemble if the update didn't change the
> primary key. So this just hits the path we'd also hit for an unchanged toasted
> non-key column.

Oh. Hmm. That's bad.

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [BUG]Update Toast data failure in logical replication
Next
From: Tomas Vondra
Date:
Subject: Re: Bug in ProcArrayApplyRecoveryInfo for snapshots crossing 4B, breaking replicas