postgres.git / summary / log / commit / refs

commit    1bbcbfaf7824590834df7352d3aaeb4ade43be31
Author:   David Rowley <drowley@postgresql.org>
Date:     Wed Jun 12 22:35:47 2019 +0000
First released in: 12.0, 10.9, 11.4

    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 | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index dfcf3c4ab0a..12905c97211 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -3982,15 +3982,15 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate &gt;= DATE '2008-01-01';
    <para>
     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.  Planning times
-    become longer and memory consumption becomes higher as more partitions are
-    added.  This is particularly true for the <command>UPDATE</command> and
-    <command>DELETE</command> 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
-    partition requires its metadata to be loaded into the local memory of
-    each session that touches it.
+    handle partition hierarchies with up to a few hundred partitions.
+    Planning times become longer and memory consumption becomes higher as more
+    partitions are added.  This is particularly true for the
+    <command>UPDATE</command> and <command>DELETE</command> 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 partition requires its metadata to be loaded into the
+    local memory of each session that touches it.
    </para>
 
    <para>


[parent: ac8f2e1ef34f]