sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-19 00:01:45 -04:00
Code Issues Projects Releases Wiki Activity

doc: Fix grammatical error in partitioning docs

Browse Source 
Reported-by: Amit Langote
Discussion: https://postgr.es/m/CA+HiwqGZFkKi0TkBGYpr2_5qrRAbHZoP47AP1BRLUOUkfQdy_A@mail.gmail.com
Backpatch-through: 10
This commit is contained in:
David Rowley 2019-06-13 10:35:11 +12:00
parent 9680728371
commit ddc053dc50
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/ddl.sgml
View File

@ -4730,12 +4730,12 @@ EXPLAIN SELECT count(*) FROM measurement WHERE logdate >= 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 thousand 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 thousand 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 when more partitions remain after the planner
performs partition pruning. This is particularly true for the
<command>UPDATE</command> and <command>DELETE</command> commands. Another
<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.