Re: Wrong result for comparing ROW(...) with IS NOT NULL

From: Wolfgang Walther <walther(at)technowledgy(dot)de>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Wrong result for comparing ROW(...) with IS NOT NULL
Date: 2020-11-05 13:40:53
Message-ID: 2ba24707-e7ba-2ccb-7269-71202a400a70@technowledgy.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Pavel Stehule:
> for composite types this sentence is not valid
>
> https://til.cybertec-postgresql.com/post/2019-09-29-Composite-types-and-NULL-in-PostgreSQL/
>
> is null - is true, when all fields are null, and is not null is true,
> when all fields is not null.

Ok, I can see how this explanation is somehow consistent. The link you
gave is just another observation of that, though. Can I infer from
anywhere in the official docs, that this is correct and expected behaviour?

Best

Wolfgang

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Borisov 2020-11-05 13:48:23 Re: Wrong result for comparing ROW(...) with IS NOT NULL
Previous Message Pavel Stehule 2020-11-05 13:14:16 Re: Wrong result for comparing ROW(...) with IS NOT NULL