From: | "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: (possible) bug with constraint exclusion |
Date: | 2008-01-12 09:02:34 |
Message-ID: | a97c77030801120102l3bcef52di9b3cd782e7c484b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-sql |
On Jan 12, 2008 10:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com> 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:
> http://archives.postgresql.org/pgsql-committers/2008-01/msg00184.php
Thanks for the (unbelievable) quick response,
I applied the patch on my production server and the problem is gone.
tradein_clients=> \pset null NULL
Null display is "NULL".
tradein_clients=> SELECT * from temp.x where id is NULL;
id
------
NULL
(1 row)
tradein_clients=> SELECT * from temp.x ;
id
------
1
2
NULL
(3 rows)
tradein_clients=>
Regds
mallah.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | guillaume (ioguix) de Rorthais | 2008-01-12 17:13:04 | BUG #3869: A scenario where pg_dump doesn't dump sequence |
Previous Message | Tom Lane | 2008-01-12 05:24:03 | Re: (possible) bug with constraint exclusion |
From | Date | Subject | |
---|---|---|---|
Next Message | Shane Ambler | 2008-01-12 10:30:44 | Re: SQL question: Highest column value of unique column pairs |
Previous Message | Tom Lane | 2008-01-12 05:24:03 | Re: (possible) bug with constraint exclusion |