Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)

From: Hannu Krosing <hannuk(at)google(dot)com>
To: Nikita Malakhov <hukutoc(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, "Burd, Greg" <greg(at)burd(dot)me>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)
Date: 2025-07-18 22:31:03
Message-ID: CAMT0RQSxLCjQH-Y-qVOnfqDQdtYgV5LeAkvOAfmZAZbeBHRgvw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 14, 2025 at 8:15 AM Nikita Malakhov <hukutoc(at)gmail(dot)com> wrote:
>
...
> Have to mention though that we encountered issues in logical replication
> when we made toast values updatable.

This seems to indicate that Logical Decoding does not honour
visibility checks in TOAST.
This works fine if the TOAST visibility never changes but will break
if it can change independently of heap-side tuple

> Also researching direct tids implementation.

Cool!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2025-07-18 23:25:54 Re: Foreign key isolation tests
Previous Message Daniel Gustafsson 2025-07-18 22:29:08 Re: [PoC] Federated Authn/z with OAUTHBEARER