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

From Paolo Guagliardo
Subject Re: [BUGS] BUG #14717: NULL=NULL is true for composite types
Date
Msg-id 08629cd7-ba28-4369-961c-a889797139c9@ed.ac.uk
Whole thread Raw
In response to Re: [BUGS] BUG #14717: NULL=NULL is true for composite types  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
I'm really sorry, David. For some reason I overlooked that part. Thanks.

Sent from BlueMail On Jun 26, 2017, at 4:49 PM, "David G. Johnston" <david.g.johnston@gmail.com> wrote:

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.
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: "David G. Johnston"
Date:
Subject: Re: [BUGS] Problems installation
Next
From: "Caio Parolin"
Date:
Subject: RES: [BUGS] Problems installation