| From: | Yingying Chen <cyy9255(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed |
| Date: | 2026-06-17 06:28:37 |
| Message-ID: | CAGGTb65drjW5ja62OVAhXqisy29Us7bV-kgDFDKpvAN_cWBecg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 17, 2026 at 11:34 AM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
> Hi,
>
> A documentation gap was identified [1] regarding the new publication
> FOR ALL TABLES EXCEPT behaviour. e.g. what happens if an excluded
> table is renamed or moved?
>
> This patch addresses that gap.
>
> Note that the patch uses different text from what was previously
> suggested because, when I checked with AI, it proposed this much
> simpler wording.
>
> ======
> [1]
> https://www.postgresql.org/message-id/CAA4eK1J_QP8CXCshaCy_01ALQQrDSzoTHfXKcAbjiEvV-RkOOw%40mail.gmail.com
>
> Kind Regards,
> Peter Smith.
> Fujitsu Australia
>
I think this is an improvement. AFAIK, the EXCEPT behavior is based on the
table OID, and renaming a table or setting its schema does not change the
table’s OID, so the defined EXCEPT for the table is not affected.
The doc patch looks good.
Regards,
Yingying Chen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2026-06-17 07:06:43 | Re: Support EXCEPT for ALL SEQUENCES publications |
| Previous Message | Amit Kapila | 2026-06-17 06:28:22 | Re: Proposal: Conflict log history table for Logical Replication |