Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
Date
Msg-id CAA4eK1JHCjACYgtYojAr9cybKTgp7a7YwS5etnQRLV=KBfpt7w@mail.gmail.com
Whole thread
In response to Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Rename EXISTS-to-ANY converted subplan to exists_to_any
Next
From: Chao Li
Date:
Subject: Re: Fix tuple deformation with virtual generated NOT NULL columns