From e23338cec4fb088235f27949c4f298b9738877d9 Mon Sep 17 00:00:00 2001 From: David Rowley Date: Thu, 13 Jun 2019 10:35:27 +1200 Subject: [PATCH] doc: Fix grammatical error in partitioning docs Reported-by: Amit Langote Discussion: https://postgr.es/m/CA+HiwqGZFkKi0TkBGYpr2_5qrRAbHZoP47AP1BRLUOUkfQdy_A@mail.gmail.com Backpatch-through: 10 --- doc/src/sgml/ddl.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index b628cac2d3..a49a14cac1 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -4113,12 +4113,12 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate >= DATE '2008-01-01'; It is also important to consider the overhead of partitioning during query planning and execution. The query planner is generally able to - handle partition hierarchies up a few hundred partitions fairly well, - provided that typical queries allow the query planner to prune all but a - small number of partitions. Planning times become longer and memory + handle partition hierarchies with up to a few hundred partitions fairly + well, provided that typical queries allow the query planner to prune all + but a small number of partitions. Planning times become longer and memory consumption becomes higher as more partitions are added. This is particularly true for the UPDATE and - DELETE commands. Another reason to be concerned about + DELETE commands. Another reason to be concerned about having a large number of partitions is that the server's memory consumption may grow significantly over a period of time, especially if many sessions touch large numbers of partitions. That's because each