From: Chandy G <vgchandru@yahoo.com>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Toasted column values during replication. (Enhancement)
Date: Fri, 30 Jun 2023 17:10:25 +0000 (UTC)
Message-ID: <780628120.613465.1688145025701@mail.yahoo.com> (raw)
References: <780628120.613465.1688145025701.ref@mail.yahoo.com>
We are running into the postgres toasted values showing up in replication slots. We are using debezium and have gone through the following
1. Various options for handling toasted values during replication at the application level.2. Postgres option to turn on replica identitiy to full.
While these are solutions to the problem, each of them comes with their own downside of
(a) custom implementation needed for each consumer. (b) replica identity to full - wal log file size increase. worst case: all tables have columns have toastable columns.
Wanted to understand if there is any scope for enhancement / improvements in postgres itself to handle such scenarios.
Enhancement request: Can the postgres internal component (wal-sender / *) interpret this special toasted-col-value sitting in the wal-file -> replace it with the actual value and send it to the replication slot. I presume, today the wal-sender does not have this support and it just sends whatever data that the wal log has. So if the wal-sender - can intercept such toasted values and translate it to actual values before being sent - that would solve the problem without every consumer having to implement a solution to handle toasted value. This would also help prevent the unwarranted increase of the wal-log if replica-identity to full is set as a w/a.
Thanks.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: vgchandru@yahoo.com
Subject: Re: Toasted column values during replication. (Enhancement)
In-Reply-To: <780628120.613465.1688145025701@mail.yahoo.com>
References: <780628120.613465.1688145025701.ref@mail.yahoo.com> <780628120.613465.1688145025701@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox