database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code 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:47 +12:00
parent ac8f2e1ef3
commit 1bbcbfaf78
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

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