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

Hannu Krosing <hannuk@google.com>

From: Hannu Krosing <hannuk@google.com>

To: Nikita Malakhov <hukutoc@gmail.com>

Cc: Álvaro Herrera <alvherre@kurilemu.de>, Michael Paquier <michael@paquier.xyz>, "Burd, Greg" <greg@burd.me>, Postgres hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-07-18T22:31:03Z

Lists: pgsql-hackers

On Mon, Jul 14, 2025 at 8:15 AM Nikita Malakhov <hukutoc@gmail.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!