On Mon, Jan 19, 2026 at 1:20 AM Chao Li <[email protected]> wrote:
> > Thanks again for your review. I have integrated all your edits to v4. Once > you consider the changes are okay, can you please mark the CF entry [1] as > Ready for Committer? > > v5 Attached with a delta. There exists described behaviors in the notes that are being removed that need to be retained; pertaining to inheritance setups. I put a note in place of the removals pointing out that when inheritance is being used for partitioning the rules for partitioned tables apply (implied 'unless otherwise noted') and that local/independent objects can always be addressed normally. I then incorporated the notes into the appropriate sub-command sections. Please give it a sanity check since I'm still getting my head around all this. David J.
From 262a5b3418174ffb7e2295523b1a9e2235ab53b6 Mon Sep 17 00:00:00 2001 From: "David G. Johnston" <[email protected]> Date: Wed, 7 Jan 2026 14:50:36 -0700 Subject: [PATCH v5 1/2] docs: clarify ALTER TABLE behavior on partitioned tables Document how individual ALTER TABLE sub-commands behave when applied to partitioned tables. The existing ALTER TABLE documentation provides limited or incomplete information about how commands interact with partitioned tables, leaving users to infer behavior from experimentation. This patch systematically clarifies, for each relevant sub-command, whether changes propagate to existing partitions, can be applied independently to partitions, and how the ONLY keyword behaves. In addition, clarify in CREATE TABLE documentation which parent table settings are inherited by newly created partitions and which are not. This makes explicit that while most definition-level properties are inherited from the partitioned table, certain per-relation settings (such as ownership, schema, replica identity, row-level security, and per-attribute statistics/options) are not, unless explicitly specified. No behavior is changed by this patch; it is purely a documentation update intended to make existing semantics explicit and easier to understand. Author: Chao Li <[email protected]> Author: David G. Johnston <[email protected]> Reviewed-by: David G. Johnston <[email protected]> Discussion: https://postgr.es/m/CAEoWx2=myhcfsnhan96qqwq5b0gvs2ygo3zpvqpprd_io52...@mail.gmail.com --- doc/src/sgml/ref/alter_table.sgml | 298 ++++++++++++++++++++--------- doc/src/sgml/ref/create_table.sgml | 9 + 2 files changed, 214 insertions(+), 93 deletions(-) diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 1bd479c917a..6131632d20b 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -171,6 +171,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM is specified and a column already exists with this name, no error is thrown. </para> + <para> + When applied to a partitioned table, the column is added to the + partitioned table definition and is implicitly added to all + partitions. Specifying <literal>ONLY</literal> is not allowed, and + this command cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -190,6 +196,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM does not exist, no error is thrown. In this case a notice is issued instead. </para> + <para> + When applied to a partitioned table, the column is removed from the + partitioned table definition and is implicitly removed from all + partitions. Specifying <literal>ONLY</literal> is not allowed, and + this command cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -211,7 +223,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM clause must be provided if there is no implicit or assignment cast from old to new type. </para> - <para> When this form is used, the column's statistics are removed, so running <link linkend="sql-analyze"><command>ANALYZE</command></link> @@ -219,6 +230,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM For a virtual generated column, <command>ANALYZE</command> is not necessary because such columns never have statistics. </para> + <para> + When applied to a partitioned table, the data type change is applied + to the partitioned table definition and is implicitly applied to all + partitions. Specifying <literal>ONLY</literal> is not allowed, + and this command cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -232,6 +249,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM or <command>UPDATE</command> commands; it does not cause rows already in the table to change. </para> + <para> + When applied to a partitioned table, the default value is propagated + to all partitions unless <literal>ONLY</literal> is specified. + </para> </listitem> </varlistentry> @@ -242,7 +263,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM These forms change whether a column is marked to allow null values or to reject null values. </para> - <para> <literal>SET NOT NULL</literal> may only be applied to a column provided none of the records in the table contain a @@ -255,18 +275,18 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM If a column has an invalid not-null constraint, <literal>SET NOT NULL</literal> validates it. </para> - <para> - If this table is a partition, one cannot perform <literal>DROP NOT NULL</literal> - on a column if it is marked <literal>NOT NULL</literal> in the parent - table. To drop the <literal>NOT NULL</literal> constraint from all the - partitions, perform <literal>DROP NOT NULL</literal> on the parent - table. Even if there is no <literal>NOT NULL</literal> constraint on the - parent, such a constraint can still be added to individual partitions, - if desired; that is, the children can disallow nulls even if the parent - allows them, but not the other way around. It is also possible to drop - the <literal>NOT NULL</literal> constraint from <literal>ONLY</literal> - the parent table, which does not remove it from the children. + If this table is a partition, one cannot perform + <literal>DROP NOT NULL</literal> on a column if it is marked + <literal>NOT NULL</literal> in the parent table. To drop the + <literal>NOT NULL</literal> constraint from all partitions, perform + <literal>DROP NOT NULL</literal> on the parent table. Even if there is + no <literal>NOT NULL</literal> constraint on the parent, such a + constraint can still be added to individual partitions; that is, the + children can disallow nulls even if the parent allows them, but not + the other way around. It is also possible to apply + <literal>SET NOT NULL</literal> or <literal>DROP NOT NULL</literal> to + <literal>ONLY</literal> the parent table. </para> </listitem> </varlistentry> @@ -279,7 +299,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM in a stored generated column is rewritten and all the future changes will apply the new generation expression. </para> - <para> When this form is used on a stored generated column, its statistics are removed, so running @@ -288,6 +307,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM For a virtual generated column, <command>ANALYZE</command> is not necessary because such columns never have statistics. </para> + <para> + When applied to a partitioned table, the generation expression is + propagated to all partitions unless <literal>ONLY</literal> + is specified. + </para> </listitem> </varlistentry> @@ -299,17 +323,21 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM Existing data in the columns is retained, but future changes will no longer apply the generation expression. </para> - <para> This form is currently only supported for stored generated columns (not virtual ones). </para> - <para> If <literal>DROP EXPRESSION IF EXISTS</literal> is specified and the column is not a generated column, no error is thrown. In this case a notice is issued instead. </para> + <para> + When applied to a partitioned table, the generation expression is + dropped from the partitioned table definition and from all + partitions. Specifying <literal>ONLY</literal> is not allowed, and + this command cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -327,12 +355,17 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM and <command>UPDATE</command> commands; they do not cause rows already in the table to change. </para> - <para> If <literal>DROP IDENTITY IF EXISTS</literal> is specified and the column is not an identity column, no error is thrown. In this case a notice is issued instead. </para> + <para> + When applied to a partitioned table, the identity property is defined + on the partitioned table and is applied to all partitions. + Specifying <literal>ONLY</literal> is not allowed, and these forms + cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -346,6 +379,13 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM supported by <link linkend="sql-altersequence"><command>ALTER SEQUENCE</command></link> such as <literal>INCREMENT BY</literal>. </para> + <para> + When applied to a partitioned table, these forms alter the sequence + associated with the identity column on the partitioned table + and all individual partitions. Specifying <literal>ONLY</literal> + is not allowed, and these forms cannot be used on individual + partitions. + </para> </listitem> </varlistentry> @@ -369,6 +409,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <literal>SET STATISTICS</literal> acquires a <literal>SHARE UPDATE EXCLUSIVE</literal> lock. </para> + <para> + For partitioned tables, this action applies to the partitioned table + and all of its partitions unless <literal>ONLY</literal> is specified. + </para> </listitem> </varlistentry> @@ -403,6 +447,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM Changing per-attribute options acquires a <literal>SHARE UPDATE EXCLUSIVE</literal> lock. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + these forms must be applied separately to the partitioned table and/or to + individual partitions. + </para> </listitem> </varlistentry> @@ -437,6 +486,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM during future table updates. See <xref linkend="storage-toast"/> for more information. </para> + <para> + When applied to a partitioned table, the storage setting is propagated + to all existing partitions unless <literal>ONLY</literal> is specified. + </para> </listitem> </varlistentry> @@ -467,6 +520,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM consulting the <xref linkend="guc-default-toast-compression"/> setting at the time of data insertion to determine the method to use. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + the compression method must be applied separately to the partitioned table + and/or to individual partitions. + </para> </listitem> </varlistentry> @@ -479,7 +537,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM VALID</literal>, which is currently only allowed for foreign-key, <literal>CHECK</literal>, and not-null constraints. </para> - <para> Normally, this form will cause a scan of the table to verify that all existing rows in the table satisfy the new constraint. But if @@ -495,7 +552,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM See <xref linkend="sql-altertable-notes"/> below for more information about using the <literal>NOT VALID</literal> option. </para> - <para> Although most forms of <literal>ADD <replaceable class="parameter">table_constraint</replaceable></literal> @@ -506,12 +562,15 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM referenced table, in addition to the lock on the table on which the constraint is declared. </para> - <para> Additional restrictions apply when unique or primary key constraints are added to partitioned tables; see <link linkend="sql-createtable"><command>CREATE TABLE</command></link>. </para> - + <para> + When applied to a partitioned table, the constraint is added to the + partitioned table and is implicitly added to all partitions. + Specifying <literal>ONLY</literal> is not allowed. + </para> </listitem> </varlistentry> @@ -523,7 +582,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM constraint to a table based on an existing unique index. All the columns of the index will be included in the constraint. </para> - <para> The index cannot have expression columns nor be a partial index. Also, it must be a b-tree index with default sort ordering. These @@ -531,7 +589,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM built by a regular <literal>ADD PRIMARY KEY</literal> or <literal>ADD UNIQUE</literal> command. </para> - <para> If <literal>PRIMARY KEY</literal> is specified, and the index's columns are not already marked <literal>NOT NULL</literal>, then this command will attempt to @@ -539,13 +596,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM That requires a full table scan to verify the column(s) contain no nulls. In all other cases, this is a fast operation. </para> - <para> If a constraint name is provided then the index will be renamed to match the constraint name. Otherwise the constraint will be named the same as the index. </para> - <para> After this command is executed, the index is <quote>owned</quote> by the constraint, in the same way as if the index had been built by @@ -553,11 +608,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM command. In particular, dropping the constraint will make the index disappear too. </para> - <para> - This form is not currently supported on partitioned tables. + This form is not supported on partitioned tables, but can be used on + individual partitions. </para> - <note> <para> Adding a constraint using an existing index can be helpful in @@ -578,6 +632,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM created. Currently only foreign key constraints may be altered in this fashion, but see below. </para> + <para> + When applied to a partitioned table, the constraint is altered on the + partitioned table definition is implicitly applied to all partitions. + Specifying <literal>ONLY</literal> is not allowed, and this command + cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -596,7 +656,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM non-inheritable on a table with children, then the corresponding constraint on children will be marked as no longer inherited, but not removed. - </para> + </para> + <para> + These forms are not supported on partitioned tables, but can be used + on individual partitions. + </para> </listitem> </varlistentry> @@ -615,6 +679,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> This command acquires a <literal>SHARE UPDATE EXCLUSIVE</literal> lock. </para> + <para> + When applied to a partitioned table, the constraint is validated on the + partitioned table and on all partitions. Unlike most constraint-related + sub-commands, individual partitions may validate the constraint + independently of the partitioned table. + </para> </listitem> </varlistentry> @@ -627,6 +697,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM If <literal>IF EXISTS</literal> is specified and the constraint does not exist, no error is thrown. In this case a notice is issued instead. </para> + <para> + When applied to a partitioned table, the constraint is dropped from + all existing partitions unless <literal>ONLY</literal> is specified. + Individual partitions may drop constraints independently of the + partitioned table. + </para> </listitem> </varlistentry> @@ -648,7 +724,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM of course the integrity of the constraint cannot be guaranteed if the triggers are not executed. </para> - <para> The trigger firing mechanism is also affected by the configuration variable <xref linkend="guc-session-replication-role"/>. Simply enabled @@ -658,7 +733,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM mode, and triggers configured as <literal>ENABLE ALWAYS</literal> will fire regardless of the current replication role. </para> - <para> The effect of this mechanism is that in the default configuration, triggers do not fire on replicas. This is useful because if a trigger @@ -670,13 +744,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM to <literal>ENABLE ALWAYS</literal> so that it is also fired on replicas. </para> - <para> When this command is applied to a partitioned table, the states of - corresponding clone triggers in the partitions are updated too, - unless <literal>ONLY</literal> is specified. + corresponding clone triggers are updated too, unless <literal>ONLY</literal> + is specified. </para> - <para> This command acquires a <literal>SHARE ROW EXCLUSIVE</literal> lock. </para> @@ -694,12 +766,16 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM are always applied in order to keep views working even if the current session is in a non-default replication role. </para> - <para> The rule firing mechanism is also affected by the configuration variable <xref linkend="guc-session-replication-role"/>, analogous to triggers as described above. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + these forms must be applied separately to the partitioned table + and/or to individual partitions. + </para> </listitem> </varlistentry> @@ -715,6 +791,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM See also <link linkend="sql-createpolicy"><command>CREATE POLICY</command></link>. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + these forms must be applied separately to the partitioned table and/or to + individual partitions. + </para> </listitem> </varlistentry> @@ -730,6 +811,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM See also <link linkend="sql-createpolicy"><command>CREATE POLICY</command></link>. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + this form must be applied separately to the partitioned table and/or to + individual partitions. + </para> </listitem> </varlistentry> @@ -744,6 +830,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> Changing cluster options acquires a <literal>SHARE UPDATE EXCLUSIVE</literal> lock. </para> + <para> + This form is not supported on partitioned tables, but can be used on + individual partitions. + </para> </listitem> </varlistentry> @@ -759,6 +849,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> Changing cluster options acquires a <literal>SHARE UPDATE EXCLUSIVE</literal> lock. </para> + <para> + This form is not supported on partitioned tables, but can be used on + individual partitions. + </para> </listitem> </varlistentry> @@ -786,11 +880,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM </para> <para> When applied to a partitioned table, there is no data to rewrite, - but partitions created afterwards will default to the given access - method unless overridden by a <literal>USING</literal> clause. - Specifying <varname>DEFAULT</varname> removes a previous value, - causing future partitions to default to - <varname>default_table_access_method</varname>. + only the default for newly created partitions is changed. + Specifying <literal>DEFAULT</literal> removes a previously set access method, + causing future partitions to use <varname>default_table_access_method</varname>. + Individual partitions are affected just like any other regular table. </para> </listitem> </varlistentry> @@ -803,12 +896,9 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM moves the data file(s) associated with the table to the new tablespace. Indexes on the table, if any, are not moved; but they can be moved separately with additional <literal>SET TABLESPACE</literal> commands. - When applied to a partitioned table, nothing is moved, but any - partitions created afterwards with - <command>CREATE TABLE PARTITION OF</command> will use that tablespace, - unless overridden by a <literal>TABLESPACE</literal> clause. + When applied to a partitioned table, no data is moved, only the default + for newly created partitions is changed. </para> - <para> All tables in the current database in a tablespace can be moved by using the <literal>ALL IN TABLESPACE</literal> form, which will lock all tables @@ -835,15 +925,14 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM (see <xref linkend="sql-createtable-unlogged"/>). It cannot be applied to a temporary table. </para> - <para> This also changes the persistence of any sequences linked to the table (for identity or serial columns). However, it is also possible to change the persistence of such sequences separately. </para> - <para> - This form is not supported for partitioned tables. + This form is not supported on partitioned tables, but can be used on + individual partitions. </para> </listitem> </varlistentry> @@ -865,12 +954,15 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM time the table is locked so currently executing queries will not be affected. </para> - <para> <literal>SHARE UPDATE EXCLUSIVE</literal> lock will be taken for fillfactor, TOAST and autovacuum storage parameters, as well as the planner parameter <varname>parallel_workers</varname>. </para> + <para> + This form is not supported on partitioned tables, but can be used on + individual partitions. + </para> </listitem> </varlistentry> @@ -882,6 +974,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM defaults. As with <literal>SET</literal>, a table rewrite might be needed to update the table entirely. </para> + <para> + When applied to a partitioned table, this form is accepted but has no + practical effect. It can be used on individual partitions, where it + behaves as for a regular table. + </para> </listitem> </varlistentry> @@ -895,7 +992,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM already contain all the same columns as the parent (it could have additional columns, too). The columns must have matching data types. </para> - <para> In addition, all <literal>CHECK</literal> and <literal>NOT NULL</literal> constraints on the parent must also exist on the child, except those @@ -907,6 +1003,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <literal>FOREIGN KEY</literal> constraints are not considered, but this might change in the future. </para> + <para> + This form does not support partitioned tables; it cannot be applied to + either a partitioned table or its partitions. + </para> </listitem> </varlistentry> @@ -919,6 +1019,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM Queries against the parent table will no longer include records drawn from the target table. </para> + <para> + This form does not support partitioned tables; it cannot be applied to + either a partitioned table or its partitions. + </para> </listitem> </varlistentry> @@ -933,6 +1037,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM that <command>CREATE TABLE OF</command> would permit an equivalent table definition. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + and this form cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -942,6 +1050,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <para> This form dissociates a typed table from its type. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + and this form cannot be used on individual partitions. + </para> </listitem> </varlistentry> @@ -952,6 +1064,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM This form changes the owner of the table, sequence, view, materialized view, or foreign table to the specified user. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + this form must be applied separately to the partitioned table and/or to + individual partitions. + </para> </listitem> </varlistentry> @@ -1008,6 +1125,12 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM </listitem> </varlistentry> </variablelist></para> + + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + this form must be applied independently to the partitioned table and/or + to individual partitions. + </para> </listitem> </varlistentry> @@ -1022,6 +1145,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM the index is renamed as well. There is no effect on the stored data. </para> + <para> + For partitioned tables, this form behaves the same as for regular + tables. Renaming a partitioned table, column, or constraint does not + propagate to partitions. + </para> </listitem> </varlistentry> @@ -1032,6 +1160,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM This form moves the table into another schema. Associated indexes, constraints, and sequences owned by table columns are moved as well. </para> + <para> + When applied to a partitioned table <literal>ONLY</literal> is implicit, + this form must be applied independently to the partitioned table and/or + to individual partitions. + </para> </listitem> </varlistentry> @@ -1410,6 +1543,27 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM <literal>*</literal> can be specified after the table name to explicitly indicate that descendant tables are included. </para> + + <para> + For a table that uses table inheritance, descendant tables are those + that inherit from the named table, directly or indirectly. + For a partitioned table, descendant tables are its partitions. + </para> + + <para> + Note that for partitioned tables, <literal>ONLY</literal> does not control + recursion for all <command>ALTER TABLE</command> actions. Some actions + apply only to the partitioned table itself, regardless of whether + <literal>ONLY</literal> is specified, while others are propagated to + partitions. The exact behavior depends on the specific action being + performed. + </para> + + <para> + Users should consult the documentation of each individual + <command>ALTER TABLE</command> action to determine whether and how it + affects partitions. + </para> </listitem> </varlistentry> @@ -1767,48 +1921,6 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM the column. </para> - <para> - If a table has any descendant tables, it is not permitted to add, - rename, or change the type of a column in the parent table without doing - the same to the descendants. This ensures that the descendants always - have columns matching the parent. Similarly, a <literal>CHECK</literal> - constraint cannot be renamed in the parent without also renaming it in - all descendants, so that <literal>CHECK</literal> constraints also match - between the parent and its descendants. (That restriction does not apply - to index-based constraints, however.) - Also, because selecting from the parent also selects from its descendants, - a constraint on the parent cannot be marked valid unless it is also marked - valid for those descendants. In all of these cases, <command>ALTER TABLE - ONLY</command> will be rejected. - </para> - - <para> - A recursive <literal>DROP COLUMN</literal> operation will remove a - descendant table's column only if the descendant does not inherit - that column from any other parents and never had an independent - definition of the column. A nonrecursive <literal>DROP - COLUMN</literal> (i.e., <command>ALTER TABLE ONLY ... DROP - COLUMN</command>) never removes any descendant columns, but - instead marks them as independently defined rather than inherited. - A nonrecursive <literal>DROP COLUMN</literal> command will fail for a - partitioned table, because all partitions of a table must have the same - columns as the partitioning root. - </para> - - <para> - The actions for identity columns (<literal>ADD - GENERATED</literal>, <literal>SET</literal> etc., <literal>DROP - IDENTITY</literal>), as well as the actions - <literal>CLUSTER</literal>, <literal>OWNER</literal>, - and <literal>TABLESPACE</literal> never recurse to descendant tables; - that is, they always act as though <literal>ONLY</literal> were specified. - Actions affecting trigger states recurse to partitions of partitioned - tables (unless <literal>ONLY</literal> is specified), but never to - traditional-inheritance descendants. - Adding a constraint recurses only for <literal>CHECK</literal> constraints - that are not marked <literal>NO INHERIT</literal>. - </para> - <para> Changing any part of a system catalog table is not permitted. </para> diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 77c5a763d45..835f609e2a6 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -633,6 +633,15 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM concurrent operations on the partitioned table. </para> + <para> + When a new partition is created, it generally inherits the current + definition-level properties of the parent partitioned table. However, + some table properties are not inherited automatically. In particular, + properties related to ownership, schema, replica identity, row-level + security configuration, per-attribute statistics targets, and + per-attribute options are not inherited unless explicitly specified + for the partition. + </para> </listitem> </varlistentry> -- 2.43.0
From 895a3604430be79d2bf18c2d259a0ce49f3320e4 Mon Sep 17 00:00:00 2001 From: "David G. Johnston" <[email protected]> Date: Tue, 20 Jan 2026 18:01:46 -0700 Subject: [PATCH v5 2/2] 0002-delta --- doc/src/sgml/ref/alter_table.sgml | 34 +++++++++++++++++++++++++++---- 1 file changed, 30 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 6131632d20b..076da294ca1 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -202,6 +202,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM partitions. Specifying <literal>ONLY</literal> is not allowed, and this command cannot be used on individual partitions. </para> + <para> + For inheritance setups, a descendant column is removed only if both: this + is the only parent defining the column, and the column was never independently + defined. + </para> </listitem> </varlistentry> @@ -571,6 +576,11 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM partitioned table and is implicitly added to all partitions. Specifying <literal>ONLY</literal> is not allowed. </para> + <para> + For inheritance setups, the constraint is not added to child tables + unless it is a <literal>CHECK</literal> constraint with the (implicit) + <literal>INHERIT</literal> property. + </para> </listitem> </varlistentry> @@ -683,7 +693,8 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM When applied to a partitioned table, the constraint is validated on the partitioned table and on all partitions. Unlike most constraint-related sub-commands, individual partitions may validate the constraint - independently of the partitioned table. + independently of the partitioned table, so long as the partitioned + table itself is not yet validated. </para> </listitem> </varlistentry> @@ -749,6 +760,10 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM corresponding clone triggers are updated too, unless <literal>ONLY</literal> is specified. </para> + <para> + For inheritance setups <literal>ONLY</literal> is implied, though it may + be specified. + </para> <para> This command acquires a <literal>SHARE ROW EXCLUSIVE</literal> lock. </para> @@ -1146,9 +1161,13 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM There is no effect on the stored data. </para> <para> - For partitioned tables, this form behaves the same as for regular - tables. Renaming a partitioned table, column, or constraint does not - propagate to partitions. + When applied to a partitioned table, partition columns constraints + are implicitly renamed and specifying <literal>ONLY</literal> is not allowed. + </para> + <para> + For inheritance setups, index-based constraints are always considered + independent. Dependent columns and constraints are implicitly renamed + and specifying <literal>ONLY</literal> is not allowed. </para> </listitem> </varlistentry> @@ -1921,6 +1940,13 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM the column. </para> + <para> + For inheritance setups, the behavior described for partitioned tables applies + only to the dependent column(s) on the descendant table(s). It is always + allowed to target a descendant table with column altering commands on independent + columns. + </para> + <para> Changing any part of a system catalog table is not permitted. </para> -- 2.43.0
