Re: strange IS NULL behaviour - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: strange IS NULL behaviour
Date
Msg-id 20130705154801.GA3535@momjian.us
Whole thread Raw
In response to Re: strange IS NULL behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: strange IS NULL behaviour
List pgsql-hackers
On Fri, Jul  5, 2013 at 11:03:56AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Thu, Jul  4, 2013 at 04:29:20PM -0400, Tom Lane wrote:
> >> No, it isn't, or at least it's far from the only place.  If we're going
> >> to change this, we would also want to change the behavior of tests on
> >> RECORD values, which is something that would have to happen at runtime.
> 
> > I checked RECORD and that behaves with recursion:
> 
> Apparently you don't even understand the problem.  All of these examples
> you're showing are constants.  Try something like
> 
>     declare r record;
>     ...
>     select ... into r ...
>     if (r is null) ...

Not aparently --- I already said I didn't understand the problem. 
Should I just mark this as a TODO?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Steve Singer
Date:
Subject: Re: changeset generation v5-01 - Patches & git tree
Next
From: Andres Freund
Date:
Subject: Re: changeset generation v5-01 - Patches & git tree