DOCS - Clarify behaviour when EXCEPT tables are moved/renamed

Started by Peter Smith7 days ago6 messageshackers
Jump to latest
#1Peter Smith
smithpb2250@gmail.com

Hi,

A documentation gap was identified [1]/messages/by-id/CAA4eK1J_QP8CXCshaCy_01ALQQrDSzoTHfXKcAbjiEvV-RkOOw@mail.gmail.com 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]: /messages/by-id/CAA4eK1J_QP8CXCshaCy_01ALQQrDSzoTHfXKcAbjiEvV-RkOOw@mail.gmail.com

Kind Regards,
Peter Smith.
Fujitsu Australia

Attachments:

v1-0001-DOCS-clarify-behaviour-when-EXCEPT-tables-are-ren.patchapplication/octet-stream; name=v1-0001-DOCS-clarify-behaviour-when-EXCEPT-tables-are-ren.patchDownload+4-1
#2Yingying Chen
cyy9255@gmail.com
In reply to: Peter Smith (#1)
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed

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]
/messages/by-id/CAA4eK1J_QP8CXCshaCy_01ALQQrDSzoTHfXKcAbjiEvV-RkOOw@mail.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

#3Amit Kapila
amit.kapila16@gmail.com
In reply to: Peter Smith (#1)
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed

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.

#4Peter Smith
smithpb2250@gmail.com
In reply to: Amit Kapila (#3)
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed

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

Attachments:

v2-0001-DOCS-clarify-behaviour-when-EXCEPT-tables-are-ren.patchapplication/octet-stream; name=v2-0001-DOCS-clarify-behaviour-when-EXCEPT-tables-are-ren.patchDownload+6-1
#5Amit Kapila
amit.kapila16@gmail.com
In reply to: Peter Smith (#4)
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed

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.

#6Peter Smith
smithpb2250@gmail.com
In reply to: Amit Kapila (#5)
Re: DOCS - Clarify behaviour when EXCEPT tables are moved/renamed

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