From: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: (possible) bug with constraint exclusion
Date: Sat, 12 Jan 2008 14:32:34 +0530
Message-ID: <a97c77030801120102l3bcef52di9b3cd782e7c484b@mail.gmail.com> (raw)
In-Reply-To: <1442.1200115443@sss.pgh.pa.us>
References: <a97c77030801102258y3d501045u6b31afe0541997db@mail.gmail.com>
<23924.1200081368@sss.pgh.pa.us>
<a97c77030801112100w1c4c4fadwb5eaeab52ad4fe7e@mail.gmail.com>
<1442.1200115443@sss.pgh.pa.us>
On Jan 12, 2008 10:54 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Rajesh Kumar Mallah" <mallah.rajesh@gmail.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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mallah.rajesh@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: (possible) bug with constraint exclusion
In-Reply-To: <a97c77030801120102l3bcef52di9b3cd782e7c484b@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox