Re: Bug with plpgsql handling of NULL argument of compound type

Tom Lane wrote:
> Merlin Moncure  writes:
> > Not sure we are guided there.  Currently we follow the spec
> > specifically with the IS NULL operator but not in other cases.
> 
> Yeah.  ExecEvalNullTest() has been taught about this, but most other
> places that check null-ness just check overall datum null-ness without
> any concern for composite types.  This is a stopgap situation, obviously.

On this topic, see also 
https://www.postgresql.org/message-id/20160708024746.1410.57282@wrigleys.postgresql.org


-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services