| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Chandy G <vgchandru(at)yahoo(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Toasted column values during replication. (Enhancement) |
| Date: | 2023-07-03 08:50:27 |
| Message-ID: | CAA4eK1L6vGoBt3tuN5cJBFh3sDaXDGnQ_31JtCHWvNT1o9RBSQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jun 30, 2023 at 10:40 PM Chandy G <vgchandru(at)yahoo(dot)com> wrote:
>
> 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.
>
Which operation are you referring here (insert/update/delete)? It
seems for changed toasted values, we already construct a tuple by
retrieving toast chunks. Are you referring to unchanged toasted
values?
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hape Hape | 2023-07-03 09:43:21 | group by can use alias from select list but not the having clause |
| Previous Message | PG Bug reporting form | 2023-07-03 08:41:05 | BUG #18013: Failed installing |