Postgres Pro
Downloads
Home   >   mailing lists

Re: [BUGS] BUG #14717: NULL=NULL is true for composite types - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: [BUGS] BUG #14717: NULL=NULL is true for composite types
Date
Msg-id CAKFQuwZsXZm40affpthUi9oBVyPYG8KVrv5qF4QGjdzbSsu0Rw@mail.gmail.com
Whole thread Raw
In response to [BUGS] BUG #14717: NULL=NULL is true for composite types  (paolo.guagliardo@ed.ac.uk)
Responses Re: [BUGS] BUG #14717: NULL=NULL is true for composite types  (Paolo Guagliardo <paolo.guagliardo@ed.ac.uk>)
List pgsql-bugs
Tree view
On Mon, Jun 26, 2017 at 8:29 AM, <paolo.guagliardo@ed.ac.uk> wrote:
The following bug has been logged on the website:

Bug reference:      14717
Logged by:          Paolo Guagliardo
Email address:      paolo.guagliardo@ed.ac.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.

pgsql-bugs by date:

Previous
From: "Caio Parolin"
Date:
Subject: RES: [BUGS] Problems installation
Next
From: "David G. Johnston"
Date:
Subject: Re: [BUGS] Problems installation