upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-07-07 08:41:01 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: clarify MERGE PARTITIONS adjacency requirement

Browse source 
The existing description says the ranges of merged range-partitions
"must be adjacent" only under the heading "If the DEFAULT partition is
not in the list of merged partitions".  That could be misread as
a restriction tied to the presence of a default partition.  In fact,
merging non-adjacent ranges is rejected regardless of whether
the partitioned table has a default partition; spell that out explicitly.

Also, this commit removes a small redundancy in the documentation sentence
stating that "merged range-partitions" are "to be merged".

Reported-by: Justin Pryzby <pryzby@telsasoft.com>
Discussion: https://postgr.es/m/aj6BPoziSb-F8aJz%40pryzbyj2023
Reported-by: Pavel Borisov <pashkin.elfe@gmail.com>
Backpatch-through: 19
This commit is contained in:
Alexander Korotkov 2026-06-30 22:29:43 +03:00
parent 2ef57e636f
commit 57f19774d6
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/src/sgml/ref/alter_table.sgml
View file

@ -1206,7 +1206,8 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
<listitem>
<para>
For range-partitioned tables, the ranges of merged partitions
must be adjacent in order to be merged.
must be adjacent; this applies even if the partitioned table
has no default partition.
The partition bounds of merged partitions are combined to form the new partition bound for
<replaceable class="parameter">partition_name</replaceable>.
</para>