Thread
Commits
-
Doc: Clarify that publication exclusions track table identity.
- 77b6dd909252 19 (unreleased) landed
-
DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
Peter Smith <smithpb2250@gmail.com> — 2026-06-17T03:33:55Z
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
-
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
Yingying Chen <cyy9255@gmail.com> — 2026-06-17T06:28:37Z
On Wed, Jun 17, 2026 at 11:34 AM Peter Smith <smithpb2250@gmail.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
-
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
Amit Kapila <amit.kapila16@gmail.com> — 2026-06-17T07:23:20Z
On Wed, Jun 17, 2026 at 9:04 AM Peter Smith <smithpb2250@gmail.com> wrote: > > 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. > I find the previous wording proposed by me better as it has some explanation especially: "Once a table is excluded, the exclusion applies to that table itself, regardless of its name or schema", So ideally, we can keep the wording proposed or adjust with some explanation using the above part. -- With Regards, Amit Kapila.
-
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
Peter Smith <smithpb2250@gmail.com> — 2026-06-17T22:46:27Z
On Wed, Jun 17, 2026 at 5:23 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Wed, Jun 17, 2026 at 9:04 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > 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. > > > > I find the previous wording proposed by me better as it has some > explanation especially: "Once a table is excluded, the exclusion > applies to that table itself, regardless of its name or schema", So > ideally, we can keep the wording proposed or adjust with some > explanation using the above part. > PSA patch v2. ====== Kind Regards, Peter Smith. Fujitsu Australia
-
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
Amit Kapila <amit.kapila16@gmail.com> — 2026-06-18T02:34:58Z
On Thu, Jun 18, 2026 at 4:16 AM Peter Smith <smithpb2250@gmail.com> wrote: > > On Wed, Jun 17, 2026 at 5:23 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Wed, Jun 17, 2026 at 9:04 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > > > 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. > > > > > > > I find the previous wording proposed by me better as it has some > > explanation especially: "Once a table is excluded, the exclusion > > applies to that table itself, regardless of its name or schema", So > > ideally, we can keep the wording proposed or adjust with some > > explanation using the above part. > > > > PSA patch v2. > Pushed. -- With Regards, Amit Kapila.
-
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
Peter Smith <smithpb2250@gmail.com> — 2026-06-21T21:23:13Z
On Thu, Jun 18, 2026 at 2:35 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Thu, Jun 18, 2026 at 4:16 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > On Wed, Jun 17, 2026 at 5:23 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > > On Wed, Jun 17, 2026 at 9:04 AM Peter Smith <smithpb2250@gmail.com> wrote: > > > > > > > > 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. > > > > > > > > > > I find the previous wording proposed by me better as it has some > > > explanation especially: "Once a table is excluded, the exclusion > > > applies to that table itself, regardless of its name or schema", So > > > ideally, we can keep the wording proposed or adjust with some > > > explanation using the above part. > > > > > > > PSA patch v2. > > > > Pushed. > Thanks for pushing. ====== Kind Regards, Peter Smith. Fujitsu Australia