Re: Overriding the optimizer - Mailing list pgsql-performance

From Mark Kirkwood
Subject Re: Overriding the optimizer
Date
Msg-id 43A231AA.9070708@paradise.net.nz
Whole thread Raw
In response to Re: Overriding the optimizer  ("Craig A. James" <cjames@modgraph-usa.com>)
Responses Re: Overriding the optimizer  ("Craig A. James" <cjames@modgraph-usa.com>)
Re: Overriding the optimizer  (Tomasz Rybak <bogomips@post.pl>)
Re: Overriding the optimizer  ("Jim C. Nasby" <jnasby@pervasive.com>)
Re: Overriding the optimizer  (David Lang <dlang@invendra.net>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "Craig A. James"
Date:
Subject: Re: Overriding the optimizer
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Overriding the optimizer