Re: enable_indexonly - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: enable_indexonly
Date
Msg-id CA+U5nM+qvJj+VKpZv2xWRKA=uoKaRVoSySgkungw67rE50NdpA@mail.gmail.com
Whole thread Raw
In response to Re: enable_indexonly  (Thom Brown <thom@linux.com>)
Responses Re: enable_indexonly  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Fri, Apr 27, 2012 at 4:41 PM, Thom Brown <thom@linux.com> wrote:
> On 27 April 2012 16:08, Simon Riggs <simon@2ndquadrant.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


pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: enable_indexonly
Next
From: Andrew Dunstan
Date:
Subject: Re: enable_indexonly