Re: "Constraint exclusion" is not general enough - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "Constraint exclusion" is not general enough
Date
Msg-id 24484.1155002475@sss.pgh.pa.us
Whole thread Raw
In response to Re: "Constraint exclusion" is not general enough  ("Florian G. Pflug" <fgp@phlo.org>)
Responses Re: "Constraint exclusion" is not general enough
Re: "Constraint exclusion" is not general enough
List pgsql-hackers
"Florian G. Pflug" <fgp@phlo.org> writes:
> Tom Lane wrote:
>> But you don't have any cost numbers until after you've done the plan.

> Couldn't this work similar to geqo_effort? The planner could
> try planning the query using only cheap algorithmns, and if
> the cost exceeds a certain value, it'd restart, and use
> more sophisticated methods.

AFAICS this would be a net loss on average.  Most of the time, the
constraint exclusion code doesn't win, and so throwing away all your
planning work to try it is going to be a loser most of the time.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: "Constraint exclusion" is not general enough
Next
From: Rod Taylor
Date:
Subject: Re: "Constraint exclusion" is not general enough