Skip site navigation (1) Skip section navigation (2)

Re: enable_indexonly

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: enable_indexonly
Date: 2012-04-27 15:56:59
Message-ID: 4F9AC1CB.3000307@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

On 04/27/2012 11:45 AM, Simon Riggs wrote:
> 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...)

Maybe we should have the stylesheet watermark the dev docs pages.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Abbas ButtDate: 2012-04-27 16:02:53
Subject: Re: A problem with dump/restore of views containing whole row references
Previous:From: Simon RiggsDate: 2012-04-27 15:45:00
Subject: Re: enable_indexonly

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group