Re: How embarrassing: optimization of a one-shot query doesn't work - Mailing list pgsql-hackers

From Tom Lane
Subject Re: How embarrassing: optimization of a one-shot query doesn't work
Date
Msg-id 16180.1207014668@sss.pgh.pa.us
Whole thread Raw
In response to Re: How embarrassing: optimization of a one-shot query doesn't work  (Stephen Frost <sfrost@snowman.net>)
Responses Re: How embarrassing: optimization of a one-shot query doesn't work  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> Still, the performance regression here is bad enough that I think there
>> is little choice.  Comments/objections?

> I agree that we should update stable to fix this performance regression,
> given the gravity of it.  I also feel that we need to do so ASAP, to
> minimize the risk of people being affected by it.  The longer we wait on
> it the more likely someone will write something which is affected.

In the normal course of events I'd expect that we'd put out 8.3.2
in a month or so.  I'm not quite convinced that this issue is worth
speeding the cycle all by itself.  We've done that for data-loss
issues but never before for a mere performance problem.

The main reason I wanted to make some noise about this is to find out
if anyone is actually trying to call eval_const_expressions (or
relation_excluded_by_constraints, which it turned out needed to change
also) from 8.3 add-on code.  If anyone squawks we could think about a
faster update ...

            regards, tom lane

pgsql-hackers by date:

Previous
From: "Jonah H. Harris"
Date:
Subject: Re: Guessing future postgresql features
Next
From: "Alex Hunsaker"
Date:
Subject: Re: [PATCHES] [badalex@gmail.com: Re: [BUGS] Problem identifying constraints which should not be inherited]