| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical replication row filter loses unchanged toasted columns |
| Date: | 2026-08-13 15:19:08 |
| Message-ID: | CAKAnmm+13FYEvK8vQDqDQys+s5WnrdQd+=m90TP+K0=ru2sXxQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 13, 2026 at 9:50 AM Matthias van de Meent <
boekewurm+postgres(at)gmail(dot)com> wrote:
> Or, an option D: Forbid the creation (and use) of filtered publication
> table definitions for tables which contain a non-identity varlena-typed
> column (i.e. the type's typlen is -1).
>
I think it's too late for that: option A seems better until we get a proper
fix.
we should not allow users to create publications of which we know ahead of
> time that the
> data stream is likely to break on our side.
Maybe instead* we issue a warning on creation (again, until we get a real
fix, which I think is doable and probably needed for more than just this
use case)
* To be clear, I'm recommending the warning (call it option E) in addition
to option A
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-08-13 15:21:13 | Re: Handle MAXSTRLEN consistently |
| Previous Message | Marcos Pegoraro | 2026-08-13 14:50:40 | Re: Correct some doc items due to the REPACK |