Re: docs: clarify ALTER TABLE behavior on partitioned tables - Mailing list pgsql-hackers

From Chao Li
Subject Re: docs: clarify ALTER TABLE behavior on partitioned tables
Date
Msg-id BA4C2371-C1E1-4E06-8719-7AED9B01EFF9@gmail.com
Whole thread Raw
In response to Re: docs: clarify ALTER TABLE behavior on partitioned tables  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: docs: clarify ALTER TABLE behavior on partitioned tables
List pgsql-hackers

> On Jan 26, 2026, at 13:38, David G. Johnston <david.g.johnston@gmail.com> wrote:
>
> On Sunday, January 25, 2026, Chao Li <li.evan.chao@gmail.com> wrote:
>
> How about this:
> ```
> <para>
>  When applied to a partitioned table to rename columns or constraints,
>  the corresponding partition columns and constraints are renamed
>  implicitly. <literal>ONLY</literal> is not allowed, and the command
>  cannot be used on individual partitions. When the rename target is the
>  table name, only the named table is renamed.
> </para>
> ```
>
> …are renamed implicitly, ONLY is not allowed, and the command cannot…(and drop the mention of table renaming).
>
> Or:
>
> “When applied to a partitioned table’s name only the parent is changed, partitions must be renamed separately.
However,column or constraint renaming must be done on the parent without ONLY, the corresponding partition columns or
constraintswill be renamed implicitly.” 
>
> I find the repeated use of “table” “name(d)” and “rename(d)” in one sentence worth avoiding.

Looks good. I just did a couple of tiny tweaks:

 * Added a comma between “table’s name” and “only”: “when applied to a partitioned table’s name, only the parent …”
 * Replaced “however” with “in contrast”.

PFA v8.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/





Attachment

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: tablecmds: reject CLUSTER ON for partitioned tables earlier
Next
From: Antonin Houska
Date:
Subject: Re: Adding REPACK [concurrently]