From 44c2e6dc79fbac78185816612b6a49c05557232b Mon Sep 17 00:00:00 2001 From: "David G. Johnston" Date: Fri, 9 Jan 2026 08:54:48 -0700 Subject: [PATCH] docs: ONLY tweaks and bulk note removal --- doc/src/sgml/ref/alter_table.sgml | 74 ++++++------------------------- 1 file changed, 14 insertions(+), 60 deletions(-) diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 75a26087eb6..adf988b420e 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -529,9 +529,9 @@ WITH ( MODULUS numeric_literal, REM at the time of data insertion to determine the method to use. - When applied to a partitioned table, the compression method must be - applied separately to the partitioned table and/or to individual partitions. - Specifying ONLY is allowed but has no effect. + When applied to a partitioned table ONLY is implicit, + the compression method must be applied separately to the partitioned table + and/or to individual partitions. However, newly created partitions inherit the compression method from the partitioned table unless they define a different compression method. @@ -903,8 +903,7 @@ WITH ( MODULUS numeric_literal, REM default_table_access_method. Specifying DEFAULT removes a previously set access method, causing future partitions to use - default_table_access_method. Specifying - ONLY is allowed but has no effect. + default_table_access_method. @@ -921,7 +920,6 @@ WITH ( MODULUS numeric_literal, REM partitions are not affected, but partitions created afterwards with CREATE TABLE PARTITION OF will use the specified tablespace unless overridden by a TABLESPACE clause. - Specifying ONLY is allowed but has no effect. All tables in the current database in a tablespace can be moved by using @@ -1062,10 +1060,8 @@ WITH ( MODULUS numeric_literal, REM definition. - When applied to a partitioned table, this form affects only the - partitioned table itself. Specifying ONLY is - allowed but has no effect, and this form cannot be used on individual - partitions. + When applied to a partitioned table ONLY is implicit, + and this form cannot be used on individual partitions. @@ -1077,10 +1073,8 @@ WITH ( MODULUS numeric_literal, REM This form dissociates a typed table from its type. - When applied to a partitioned table, this form affects only the - partitioned table itself. Specifying ONLY is - allowed but has no effect, and this form cannot be used on individual - partitions. + When applied to a partitioned table ONLY is implicit, + and this form cannot be used on individual partitions. @@ -1156,8 +1150,9 @@ WITH ( MODULUS numeric_literal, REM - For partitioned tables, this form must be applied independently to the - partitioned table and/or to individual partitions. + When applied to a partitioned table ONLY is implicit, + this form must be applied independently to the partitioned table and/or + to individual partitions. Newly created partitions do not inherit the setting from the partitioned table. @@ -1191,8 +1186,9 @@ WITH ( MODULUS numeric_literal, REM constraints, and sequences owned by table columns are moved as well. - For partitioned tables, this form must be applied independently to the - partitioned table and/or to individual partitions. + When applied to a partitioned table ONLY is implicit, + this form must be applied independently to the partitioned table and/or + to individual partitions. Newly created partitions do not inherit their schema from the partitioned table. @@ -1952,48 +1948,6 @@ WITH ( MODULUS numeric_literal, REM the column. - - 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 CHECK - constraint cannot be renamed in the parent without also renaming it in - all descendants, so that CHECK 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, ALTER TABLE - ONLY will be rejected. - - - - A recursive DROP COLUMN 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 DROP - COLUMN (i.e., ALTER TABLE ONLY ... DROP - COLUMN) never removes any descendant columns, but - instead marks them as independently defined rather than inherited. - A nonrecursive DROP COLUMN command will fail for a - partitioned table, because all partitions of a table must have the same - columns as the partitioning root. - - - - The actions for identity columns (ADD - GENERATED, SET etc., DROP - IDENTITY), as well as the actions - CLUSTER, OWNER, - and TABLESPACE never recurse to descendant tables; - that is, they always act as though ONLY were specified. - Actions affecting trigger states recurse to partitions of partitioned - tables (unless ONLY is specified), but never to - traditional-inheritance descendants. - Adding a constraint recurses only for CHECK constraints - that are not marked NO INHERIT. - - Changing any part of a system catalog table is not permitted. -- 2.34.1