Date: Fri, 16 Dec 2005 16:16:58 +1300
From: Mark Kirkwood <markir@paradise.net.nz>
Subject: Re: Overriding the optimizer
In-reply-to: <43A22BE3.6020103@modgraph-usa.com>
To: "Craig A. James" <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Message-id: <43A231AA.9070708@paradise.net.nz>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7bit
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106)
References: <200512141603.52583.blargity@gmail.com>
	<7484.1134600423@sss.pgh.pa.us> <1134629567.14248.27.camel@firebolt>
	<200512150148.16125.blargity@gmail.com>
	<1134644526.14248.60.camel@firebolt>
	<43A1C40D.8040006@paradise.net.nz> <43A1F6DB.3080805@modgraph-usa.com>
	<43A226E7.7040508@paradise.net.nz> <43A22BE3.6020103@modgraph-usa.com>

Craig A. James wrote:

> 
> What would be cool would be some way the developer could alter the plan, 
> but they way of doing so would strongly encourage the developer to send 
> the information to this mailing list.  Postgres would essentially say, 
> "Ok, you can do that, but we want to know why!"
> 

Yeah it would - an implementation I have seen that I like is where the 
developer can supply the *entire* execution plan with a query. This is 
complex enough to make casual use unlikely :-), but provides the ability 
to try out other plans, and also fix that vital query that must run 
today.....

cheers

Mark