Stephen Frost <[EMAIL PROTECTED]> writes: > * Tom Lane ([EMAIL PROTECTED]) 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers