Re: Skipping schema changes in publication - Mailing list pgsql-hackers

From Peter Smith
Subject Re: Skipping schema changes in publication
Date
Msg-id CAHut+Psy+osUZ-zPekrFnnW6+h0D_dgpssx=pDpQ03COpCc-mw@mail.gmail.com
Whole thread Raw
In response to Re: Skipping schema changes in publication  (vignesh C <vignesh21@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: alignas (C11)
Next
From: Corey Huinker
Date:
Subject: Re: Optional skipping of unchanged relations during ANALYZE?