agora inbox for pgsql-committers@postgresql.orghelp / color / mirror / Atom feed
pgsql: doc: clarify MERGE PARTITIONS adjacency requirement 2+ messages / 1 participants [nested] [flat]
* pgsql: doc: clarify MERGE PARTITIONS adjacency requirement @ 2026-06-30 19:36 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Alexander Korotkov @ 2026-06-30 19:36 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/78860fab26f1440ec4a8e31d039a88c66329196f Modified Files -------------- doc/src/sgml/ref/alter_table.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: doc: clarify MERGE PARTITIONS adjacency requirement @ 2026-06-30 19:36 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Alexander Korotkov @ 2026-06-30 19:36 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/57f19774d6c88f501c835a7772a71ca5ba2bc163 Modified Files -------------- doc/src/sgml/ref/alter_table.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-06-30 19:36 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-06-30 19:36 pgsql: doc: clarify MERGE PARTITIONS adjacency requirement Alexander Korotkov <akorotkov@postgresql.org> 2026-06-30 19:36 pgsql: doc: clarify MERGE PARTITIONS adjacency requirement Alexander Korotkov <akorotkov@postgresql.org>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox