Re: Should we add GUCs to allow partition pruning to be disabled?
David Rowley <david.rowley@2ndquadrant.com>
From: David Rowley <david.rowley@2ndquadrant.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-04-26T07:29:37Z
Lists: pgsql-hackers
Attachments
- further_enable_partition_pruning_doc_updates.patch (application/octet-stream) patch
On 25 April 2018 at 09:59, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > Amit Langote wrote: >> Although the config.sgml coverage of the new capabilities seems pretty >> good, some may find their being mentioned in 5.10 Table Partitioning >> helpful. Or if we don't want to hijack 5.10.4, maybe create a 5.10.5. > > Can you (or someone) describe what would that section contain? I've drafted and attached a patch of how I think this should look. Likely it will need some tweaking, but it is probably a good starting point for discussion. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, 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