Hi list,
It's a bug, it's patched:
http://archives.postgresql.org/pgsql-committers/2008-01/msg00184.php
I have just stumbled on the same bug today and was very happy to find a
patch; however, I have a 8.2.6 server running which of course cannot be
patched. (According to the CVS tags the
=?ISO-8859-1?Q?Christian_Schr=F6der?= [EMAIL PROTECTED] writes:
It's a bug, it's patched:
http://archives.postgresql.org/pgsql-committers/2008-01/msg00184.php
I have just stumbled on the same bug today and was very happy to find a
patch; however, I have a 8.2.6 server running which of
Tom Lane wrote:
Better look again.
Sounds like a sensible advice ... I somehow managed to find
http://archives.postgresql.org/pgsql-committers/2008-01/msg00183.php
instead of
http://archives.postgresql.org/pgsql-committers/2008-01/msg00184.php ...
Sorry for that!
Regards,
Christian
On Jan 12, 2008 10:54 AM, Tom Lane [EMAIL PROTECTED] wrote:
Rajesh Kumar Mallah [EMAIL PROTECTED] writes:
Am I correct in understanding that the current behavior is inappropriate
and shall be corrected at some point of time in future versions ?
It's a bug, it's patched:
On Jan 12, 2008 1:26 AM, Tom Lane [EMAIL PROTECTED] wrote:
Rajesh Kumar Mallah [EMAIL PROTECTED] writes:
looks like constraint exclusion is being too aggressive in excluding null
values
Hmm, you're right. Looks like I broke it here:
Hi ,
looks like constraint exclusion is being too aggressive in excluding null values
although its well known that check constraints apply on not null values only.
Hope the minimal test session below explains the problem we facing.
BTW: we are very impressed with the performance gains we achieved
Update the phenomenon does not exists in 8.2.0 but exists in 8.2.5.
On Jan 11, 2008 12:28 PM, Rajesh Kumar Mallah [EMAIL PROTECTED] wrote:
Hi ,
looks like constraint exclusion is being too aggressive in excluding null
values
although its well known that check constraints apply on not null
