Re: documentation fixes for partition pruning, round two
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, David Rowley <david.rowley@2ndquadrant.com>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-06-01T18:57:22Z
Lists: pgsql-hackers
Pushed. I made a couple of minor changes, in particular I added the word "one" to this sentence, which was already under discussion: On 2018-May-24, Justin Pryzby wrote: > On Thu, May 24, 2018 at 11:30:40AM +0900, Amit Langote wrote: > > + possible to show the difference between a plan whose partitions have been > > + pruned and one whose partitions haven't. A typical unoptimized plan for > > + this type of table setup is: > > > > "a plan whose partitions have been pruned" sounds a bit off; maybe, "a > > plan in which partitions have been pruned". > > I wrote: > > "[...] a plan for which partitions have been pruned and for which they have > not." "it's possible to show the difference between a plan for which partitions have been pruned and *one* for which they have not." Thanks! -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Tweak partitioning documentation wording
- 12b9affb32a6 11.0 landed
-
docs: Rework sections on partition pruning/exclusion
- bebc46931a12 11.0 landed
-
Add GUC enable_partition_pruning
- 055fb8d33da6 11.0 landed