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

From paolo.guagliardo@ed.ac.uk
Subject [BUGS] BUG #14717: NULL=NULL is true for composite types
Date
Msg-id 20170626152934.17677.84281@wrigleys.postgresql.org
Whole thread Raw
Responses Re: [BUGS] BUG #14717: NULL=NULL is true for composite types  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
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:

Comparisons between row types with NULLs behave as expected:

SELECT (1,NULL) = (1,NULL);
?column? 
----------
(1 row)

However, if we now create a composite type:

CREATE TYPE pair AS (a int, b int);

then we get

SELECT (1,NULL)::pair = (1,NULL)::pair ;
?column? 
----------t
(1 row)

while the answer should be NULL (unknown) as before.

Other operations (<>,>,<,>=,<=) are affected as well.


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Greg Stark
Date:
Subject: Re: [BUGS] Bus error in formatting.c NUM_numpart_to_char (9.4.12, 9.6.3, sparc)
Next
From: Andres Freund
Date:
Subject: Re: [BUGS] BUG #14714: long running sessions from remote instanceseems to hang some times