Re: BUG #14717: NULL=NULL is true for composite types

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: paolo(dot)guagliardo(at)ed(dot)ac(dot)uk
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14717: NULL=NULL is true for composite types
Date: 2017-06-26 15:49:26
Message-ID: CAKFQuwZsXZm40affpthUi9oBVyPYG8KVrv5qF4QGjdzbSsu0Rw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 26, 2017 at 8:29 AM, <paolo(dot)guagliardo(at)ed(dot)ac(dot)uk> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 14717
> Logged by: Paolo Guagliardo
> Email address: paolo(dot)guagliardo(at)ed(dot)ac(dot)uk
> PostgreSQL version: 9.6.3
> Operating system: Scientific Linux release 7.3 (Nitrogen)
> Description:
>
> ​[...]

> SELECT (1,NULL)::pair = (1,NULL)::pair ;
>
> ?column?
> ----------
> t
> (1 row)
>
> while the answer should be NULL (unknown) as before.
>

Working as documented.

https://www.postgresql.org/docs/9.6/static/functions-comparisons.html

See the last two sections for why (or at least how...) "anonymous row
constructor" and "named record" are treated differently.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2017-06-26 15:51:04 Re: Problems installation
Previous Message Caio Parolin 2017-06-26 15:44:33 RES: Problems installation