diff options
| author | Magnus Hagander | 2024-01-11 13:27:10 +0000 |
|---|---|---|
| committer | Magnus Hagander | 2024-01-11 13:35:57 +0000 |
| commit | 18d51c0bb19097191182e57bc755c197ee6a4fc4 (patch) | |
| tree | ce80a32b54af0620f0001283ac0b3412f12156df | |
| parent | 469d836a90cca12e730512a445e1d78b9bc6039e (diff) | |
Fix omission in partitioning limitation documentation
UNIQUE and PRIMARY KEY constraints can be created on ONLY the
partitioned table. We already had an example demonstrating that,
but forgot to mention it in the documentation of the limits of
partitioning.
Author: Laurenz Albe
Reviewed-By: shihao zhong, Shubham Khanna, Ashutosh Bapat
Backpatch-through: 12
Discussion: https://postgr.es/m/167299368731.659.16130012959616771853@wrigleys.postgresql.org
| -rw-r--r-- | doc/src/sgml/ddl.sgml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 3a53b55ca41..08b8d3797ed 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -4144,7 +4144,9 @@ ALTER INDEX measurement_city_id_logdate_key Using <literal>ONLY</literal> to add or drop a constraint on only the partitioned table is supported as long as there are no partitions. Once partitions exist, using <literal>ONLY</literal> - will result in an error. Instead, constraints on the partitions + will result in an error for any constraints other than + <literal>UNIQUE</literal> and <literal>PRIMARY KEY</literal>. + Instead, constraints on the partitions themselves can be added and (if they are not present in the parent table) dropped. </para> |