| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | 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: | DOCS - Clarify behaviour when EXCEPT tables are moved/renamed |
| Date: | 2026-06-17 03:33:55 |
| Message-ID: | CAHut+PvQ5BqnawCQd6r1tqqd+iAJC-CuRY8wscuXSrpHGUzofA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Kind Regards,
Peter Smith.
Fujitsu Australia
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-DOCS-clarify-behaviour-when-EXCEPT-tables-are-ren.patch | application/octet-stream | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2026-06-17 03:38:10 | Re: Support EXCEPT for TABLES IN SCHEMA publications |
| Previous Message | jian he | 2026-06-17 03:27:31 | Re: Fix bug of CHECK constraint enforceability recursion |