Prev: 9.0beta2 - server crash when using HS + SR
Next: Patch to show individual statement latencies in pgbenchoutput
From: Ian Barwick on 13 Jun 2010 19:15
2010/6/1 Bruce Momjian <bruce(a)momjian.us>:
> Tom Lane wrote:
(...)
>> The index-based-max code is throwing in the IS NOT NULL condition
>> without thought for where it has to go in the index condition order.
>> Will look into fixing this tomorrow.
>
> FYI, this no longer throws an error in current CVS so was fixed by Tom.

Thanks for the update, I can confirm the issue no longer occurs in
beta2.

Regards

Ian Barwick

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: 9.0beta2 - server crash when using HS + SR
Next: Patch to show individual statement latencies in pgbenchoutput