public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Chao Li <[email protected]>
Cc: Postgres hackers <[email protected]>
Cc: Amit Kapila <[email protected]>
Subject: Re: docs: clarify ALTER TABLE behavior on partitioned tables
Date: Mon, 12 Jan 2026 17:20:28 -0700
Message-ID: <CAKFQuwZaquUrTOhfmJ2CenwiyAHx4nORQ0kB01sL+z5pCBuLFQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAEoWx2=mYhCfsnHaN96Qqwq5b0GVS2YgO3zpVqPPRd_iO52wRw@mail.gmail.com>
<[email protected]>
<CAKFQuwbWNCX1M1e9_-3P9RVGo10huPjuqdL74FJ+-a5EW791KA@mail.gmail.com>
<[email protected]>
<CAKFQuwZ+o6La5DyK9_-L2gpeiKNvGMbR78UjocO4++JkyZaRHw@mail.gmail.com>
<[email protected]>
<CAKFQuwabxFyFQob=RfKOV3upjxwomAzmGzSouN-h2ypuXz+dZg@mail.gmail.com>
<[email protected]>
On Sun, Jan 11, 2026 at 10:52 PM Chao Li <[email protected]> wrote:
>
> [1] https://postgr.es/m/[email protected]
> If we stop here, these inconsistencies will remain indefinitely, which I
> believe nobody really wants. With that in mind, I’d like to suggest a
> two-phase approach.
>
> Phase 1: Document current behavior and set expectations
>
> * Identify all ALTER TABLE actions involved in these inconsistencies.
> * Update the ALTER TABLE and CREATE TABLE documentation to clearly
> describe the current behavior for partitioned tables, and (where
> appropriate) the intended or ideal behavior.
> * Explicitly document the meaning of ONLY for partitioned tables, and note
> that some actions may behave differently, with details described in each
> action’s section.
I agree, we should modify alter to note the cascade and/or non-cascade
scenarios and modify create to note the things that are (not) inherited.
I'm fine with the "newly created" stuff being put into create table instead
of touching 5.12.
We should not be documenting "ideal behavior" - only actual behavior.
We should indeed document that ONLY, if added to an alter command that
would cascade to partitions, prevents that cascading. If added to a
command that wouldn't cascade anyway it is usually accepted as just
specifying the default behavior. There is no way to indicate explicitly
that one wishes to cascade.
I still have my doubts whether changing long-standing behavior is going to
happen. But that is also fairly immaterial since best practice is to
proceed without even trying to predict the future and instead just deal
with what is in front of us right now.
David J.
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: docs: clarify ALTER TABLE behavior on partitioned tables
In-Reply-To: <CAKFQuwZaquUrTOhfmJ2CenwiyAHx4nORQ0kB01sL+z5pCBuLFQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox