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

From Florian G. Pflug
Subject Re: "Constraint exclusion" is not general enough
Date
Msg-id 44D7D267.7040506@phlo.org
Whole thread Raw
In response to Re: "Constraint exclusion" is not general enough  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "Constraint exclusion" is not general enough
List pgsql-hackers
Tom Lane wrote:
> Rod Taylor <pg@rbt.ca> writes:
>> A simple way of doing this might be to use a minimum cost number?
> 
> 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.

greetings, Florian Pflug


pgsql-hackers by date:

Previous
From: Lukas Smith
Date:
Subject: Re: PostgreSQL performance enhancement when query planner fails to
Next
From: Tom Lane
Date:
Subject: Re: "Constraint exclusion" is not general enough