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

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