Re: Skipping schema changes in publication

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, YeXiu <1518981153(at)qq(dot)com>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Skipping schema changes in publication
Date: 2026-01-29 21:36:53
Message-ID: CAHut+Psy+osUZ-zPekrFnnW6+h0D_dgpssx=pDpQ03COpCc-mw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Vignesh/Shlok.

1.
I've changed the name of the CF entry [1] for this because EXCEPT
(column-list) is no longer part of the current focus.

BEFORE
Support EXCEPT tables and EXCEPT (column-list) in publications
AFTER
Support EXCEPT tables in publications

2.
I understand the latest patch structure to be like:

0001 + 0002 (approach #1)
or
0001 + 0002 (approach #3)

AFAICT, this is breaking the CF bot, which attempts to apply all
patches at once [2]. IMO, next time you should change the patch suffix
of "0002 (approach #3)" to something like ".txt" or ".nocfbot", so
CFbot won't see it, and we can continue to get CI results for the
other patches.

======
[1] https://commitfest.postgresql.org/patch/6099/
[2] https://cfbot.cputube.org/patch_6099.log

Kind Regards,
Peter Smith.
Fujitsu Australia

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2026-01-29 21:40:28 Re: Optional skipping of unchanged relations during ANALYZE?
Previous Message Tom Lane 2026-01-29 21:19:27 Re: alignas (C11)