From b60a0d867443af7ab45ec70de5d65df8f93ab90f Mon Sep 17 00:00:00 2001 From: Alexander Korotkov Date: Fri, 26 Jun 2026 22:44:01 +0300 Subject: [PATCH v1] doc: clarify MERGE PARTITIONS adjacency requirement The existing description says the ranges of merged range-partitions "must be adjacent in order to be merged" only under the heading "If the DEFAULT partition is not in the list of merged partitions", which can 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. Reported-by: Justin Pryzby Discussion: https://postgr.es/m/aj6BPoziSb-F8aJz%40pryzbyj2023 --- doc/src/sgml/ref/alter_table.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 67a05593140..0df7396f268 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -1196,7 +1196,8 @@ WITH ( MODULUS numeric_literal, REM For range-partitioned tables, the ranges of merged partitions - must be adjacent in order to be merged. + must be adjacent in order to be merged; 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 partition_name. -- 2.39.5 (Apple Git-154)