pgsql: Clarify SPLIT PARTITION bound requirements in docs - Mailing list pgsql-committers

From Alexander Korotkov
Subject pgsql: Clarify SPLIT PARTITION bound requirements in docs
Date
Msg-id E1wPI6O-000GEt-2Y@gemulon.postgresql.org
Whole thread
List pgsql-committers
Clarify SPLIT PARTITION bound requirements in docs

The documentation said that the bounds of new partitions should not
overlap and that their combined bounds should equal the bounds of the
split partition.  That is misleading when a new DEFAULT partition is
specified, because the explicit partitions may cover only part of the
split partition while the DEFAULT partition covers the rest.

Clarify that new non-DEFAULT partition bounds must not overlap with
other new or existing partitions and must be contained within the bounds
of the split partition.  Also state that the combined bounds must exactly
match the split partition only when no new DEFAULT partition is specified.

While here, improve nearby wording about hash-partitioned target tables
and splitting a DEFAULT partition with the same partition name.

Author: Chao Li <lic@highgo.com>
Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com>
Discussion: https://postgr.es/m/C18878AB-DEB2-4A61-9995-A035DD644B81@gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/83df16f1fa5ccce72534ddad51fd0109da1e49e2

Modified Files
--------------
doc/src/sgml/ref/alter_table.sgml | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)


pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: Fix COPY FROM ON_ERROR SET_NULL with selective column list
Next
From: Álvaro Herrera
Date:
Subject: pgsql: Fix REPACK decoding worker not cleaned up on FATAL exit