]> git.ipfire.org Git - thirdparty/postgresql.git/commit
doc: clarify MERGE PARTITIONS adjacency requirement
authorAlexander Korotkov <akorotkov@postgresql.org>
Tue, 30 Jun 2026 19:29:43 +0000 (22:29 +0300)
committerAlexander Korotkov <akorotkov@postgresql.org>
Tue, 30 Jun 2026 19:30:34 +0000 (22:30 +0300)
commit57f19774d6c88f501c835a7772a71ca5ba2bc163
treebc74049e880b23fb67076ccd67265aadac2a9fcb
parent2ef57e636fc97528a37515673f5f56a1fcf97186
doc: clarify MERGE PARTITIONS adjacency requirement

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
doc/src/sgml/ref/alter_table.sgml