@@ -3982,15 +3982,15 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate >= DATE '2008-01-01';
39823982 <para>
39833983 It is also important to consider the overhead of partitioning during
39843984 query planning and execution. The query planner is generally able to
3985- handle partition hierarchies up a few hundred partitions. Planning times
3986- become longer and memory consumption becomes higher as more partitions are
3987- added. This is particularly true for the <command>UPDATE</command> and
3988- <command>DELETE</command> commands.Another reason to be concerned about
3989- having a large number of partitions is that the server's memory
3990- consumption may grow significantly over a period of time, especially if
3991- many sessions touch large numbers of partitions. That's because each
3992- partition requires its metadata to be loaded into the local memory of
3993- each session that touches it.
3985+ handle partition hierarchieswith upto a few hundred partitions.
3986+ Planning times become longer and memory consumption becomes higher as more
3987+ partitions are added. This is particularly true for the
3988+ <command>UPDATE</command> and <command> DELETE</command> commands. Another
3989+ reason to be concerned about having a large number of partitions is that
3990+ the server's memory consumption may grow significantly over a period of
3991+ time, especially if many sessions touch large numbers of partitions.
3992+ That's because each partition requires its metadata to be loaded into the
3993+ local memory of each session that touches it.
39943994 </para>
39953995
39963996 <para>