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

From: Mingjie Gao <mingjie(dot)gmj(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH v1] Fix initial sync of zero-column published tables
Date: 2026-11-05 02:48:05
Message-ID: CAL5_ZS2jbn_rhnNUBff9LurTFcc+=TJk=4OZtTZY-+iN399Qjw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Peter,

Thanks for reproducing the issue and testing the patch.

> Now that BeginCopyFrom is just a thin "wrapper" should all that
> commentary describing each of the function parameters be moved to
> BeginCopyFromExtended function-comment where all the work is done?

Agreed. I've moved the parameter descriptions to the comment for
BeginCopyFromExtended().

> The TAP test code for this patch seems more elaborate than usual.
> AFAIK it is normal to accept that regressions show up as a timeout.

I've simplified the test to use wait_for_subscription_sync(). It still
checks both text and binary modes, and retains the incremental insert check
alongside the initial sync check.

Please find the updated v2 patch attached.

Best regards,
mingjiegao

Attachment Content-Type Size
v2-0001-Fix-initial-sync-of-zero-column-published-tables.patch text/x-patch 7.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Yugo Nagata 2026-11-05 02:25:58 Re: Track skipped tables during autovacuum and autoanalyze