Re: enable_indexonly
От | Magnus Hagander |
---|---|
Тема | Re: enable_indexonly |
Дата | |
Msg-id | CABUevExPj50fKpH+DnOr-EY4HTAiGF2ip7yu=okUgaDbqnuiLQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: enable_indexonly (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: enable_indexonly
|
Список | pgsql-hackers |
On Fri, Apr 27, 2012 at 17:56, Andrew Dunstan <andrew@dunslane.net> wrote: > > > On 04/27/2012 11:45 AM, Simon Riggs wrote: >> >> 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...) > > > Maybe we should have the stylesheet watermark the dev docs pages. Are you offering to write the patch? ;) (if someone can provide a CSS that will look good and work cross browser, I can do the website code side of things that enables it for the devel docs) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: