| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: Logical replication row filter loses unchanged toasted columns |
| Date: | 2026-09-07 15:42:42 |
| Message-ID: | CALDaNm24+gk7vv_McmX9cw8P+5kCfQdMNERTC0up_Zn53Vs6_Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2 Sept 2026 at 16:02, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> Agreed. Let's start a separate thread for this case.
I have started a new thread for this issue at [1].
[1] - https://www.postgresql.org/message-id/flat/CALDaNm2-UtYX%2BpFQMEn44bpgZwYX9F9kV2Q4%2BHnC0TWp-Nx3ig%40mail.gmail.com
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florin Irion | 2026-09-07 15:55:29 | Re: pg_upgrade_replica: avoid full re-clone of standbys after pg_upgrade |
| Previous Message | vignesh C | 2026-09-07 15:34:39 | Re: Logical replication can lose an update after concurrent index invalidation |