Re: strange IS NULL behaviour

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Bruce Momjian <bruce@momjian.us>

Cc: Hannu Krosing <hannu@2ndQuadrant.com>, Peter Eisentraut <peter_e@gmx.net>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2013-07-05T15:03:56Z

Lists: pgsql-hackers

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) ...

			regards, tom lane