Re: Initial table sync copies the whole table when it is no longer published

From: Ajin Cherian <itsajin(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta malik <shvetamalik(at)gmail(dot)com>
Subject: Re: Initial table sync copies the whole table when it is no longer published
Date: 2026-11-18 01:12:07
Message-ID: CAFPTHDb2tmacHQkcf36F2pnOU74YkxkWfBL7xvu3d3pz34EBgw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 17, 2026 at 9:03 PM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> Yes, the ERROR repeats until it is resolved, but that is the same
> behaviour as other tablesync errors (e.g. "table \"%s.%s\" not found
> on publisher"). The errors are also counted in
> pg_stat_subscription_stats, so users can monitor them.
>
> With the ERROR, the table stays in the 'd' (data sync) state, which is
> the correct state IMO. With a WARNING and skip, the table would
> wrongly be marked 'ready' instead, so its initial data would never be
> copied, even after a REFRESH PUBLICATION (provided the table is added
> back or the publication is created).
>
Hi Shveta,

Just curious: with disable_on_error = true, this ERROR would disable
the whole subscription, and REFRESH PUBLICATION isn't allowed on a
disabled subscription. How would the user get out of that? If the user
re-enables the subscription, it's a race between the tablesync worker
hitting the error again and the user running REFRESH PUBLICATION.

I understand the same is true of other tablesync errors caused by
publisher-side changes (e.g. "table ... not found on publisher"), so
this isn't really related to this patch. But maybe we should document
somewhere how to get out of such situations.

Regards,
Ajin Cherian
Fujitsu Australia

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Koshino Taiki 2026-11-18 01:53:30 Re: Proposal: Include CHECK constraint expression in violation error DETAIL
Previous Message Ajin Cherian 2026-11-17 23:48:01 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade