Re: Should we warn against using too many partitions?
David Rowley <david.rowley@2ndquadrant.com>
From: David Rowley <david.rowley@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-06-09T05:07:39Z
Lists: pgsql-hackers
Attachments
- part_doc_master_v3.patch (application/octet-stream) patch v3
- part_doc_pg11_v3.patch (application/octet-stream) patch v3
- part_doc_pg10_v3.patch (application/octet-stream) patch v3
On Sun, 9 Jun 2019 at 16:21, Justin Pryzby <pryzby@telsasoft.com> wrote: > I meant it should say "into which it should be divided" and not "by which it > should be divided INTO", which has too many prepositions. This is still an > issue: It now reads "divided by" instead of "divided into". > | these two types of workload, it is important to make the right decisions > | early, as re-partitioning large quantities of data can be ... I've added a comma after "early". -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
doc: Fix grammatical error in partitioning docs
- 1bbcbfaf7824 10.9 landed
- e23338cec4fb 11.4 landed
- ddc053dc503a 12.0 landed
-
doc: Add best practises section to partitioning docs
- 6e1dc84533e4 10.9 landed
- 936b5e589e04 11.4 landed
- e788e849addd 12.0 landed