Re: [PATCH v1] Fix initial sync of zero-column published tables

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Mingjie Gao <mingjie(dot)gmj(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH v1] Fix initial sync of zero-column published tables
Date: 2026-11-19 04:35:29
Message-ID: CALDaNm2qo=J1VULfeoqXgskYpA4UQD1to6=5_hGPqQWGtu03yQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 18 Nov 2026 at 14:45, Mingjie Gao <mingjie(dot)gmj(at)gmail(dot)com> wrote:
>
> Hi Vignesh,
>
> Thanks for the suggestion. I've expanded the commit message to explain
> why COPY treats an empty column list as unspecified, the behavior in
> text and binary mode, and how tablesync marks the list as explicit.
>
> Attached is v4, rebased on master at f03a0f87963. There are no code
> changes from v3. With assertions enabled, the core regression tests,
> file_fdw regression test, and subscription TAP suite all passed.

Thanks for the updated version. This issue exists in all the supported
versions till PG15 branch, but the patch does not apply cleanly there.
Could you share a separate patch for PG15?

Regards,
Vignesh

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-11-19 04:36:44 Re: Report oldest xmin source when autovacuum cannot remove tuples
Previous Message Fujii Masao 2026-11-19 04:34:31 Re: [PATCH] Check interrupts while draining received WAL