From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: enable_indexonly |
Date: | 2012-04-27 15:45:00 |
Message-ID: | CA+U5nM+qvJj+VKpZv2xWRKA=uoKaRVoSySgkungw67rE50NdpA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 27, 2012 at 4:41 PM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 27 April 2012 16:08, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> I notice that there isn't a parameter called enable_indexonly (or similar).
>>
>> ISTM that such a major new feature should be controlled by a planner
>> method parameter, just as all the existing planner methods are.
>>
>> This will help us evaluate index only scans in production, and turn
>> them off if they have negative impacts.
>
> It already exists and is called "enable_indexonlyscan".
Hmm. Forgive me, I pressed the wrong button and looked at current docs
rather than dev docs.
(Easier when they used to look different...)
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2012-04-27 15:56:59 | Re: enable_indexonly |
Previous Message | Thom Brown | 2012-04-27 15:41:01 | Re: enable_indexonly |