| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Should we add GUCs to allow partition pruning to be disabled? |
| Date: | 2018-05-12 15:30:11 |
| Message-ID: | 20180512153011.4yjbwkbo3bpbqpdd@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
Amit Langote wrote:
> +1 to this more radical overhaul of this part of the documentation.
Thanks. I pushed now after some more tweaking, including your suggested
corrections. I removed the examples, because they were both wrong. We
can give this more polish if anybody has the energy, but I think we're
in a pretty decent place now.
I'm not convinced that we need to show so much detail on pruning as
proposed by Robert elsewhere; we didn't have a lot of detail for
exclusion either and I don't have any evidence that it was a terrible
problem for users. Also, one possible use of the new GUC is that you
can compare plans if you so wish.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-05-12 17:11:37 | Re: pg_locale compilation error with Visual Studio 2017 |
| Previous Message | Michael Paquier | 2018-05-12 12:36:16 | Re: pg_locale compilation error with Visual Studio 2017 |