Re: Bug with plpgsql handling of NULL argument of compound type - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Bug with plpgsql handling of NULL argument of compound type
Date
Msg-id 20160722194627.GA183946@alvherre.pgsql
Whole thread Raw
In response to Re: Bug with plpgsql handling of NULL argument of compound type  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug with plpgsql handling of NULL argument of compound type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Merlin Moncure <mmoncure@gmail.com> 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: fixes for the Danish locale
Next
From: Tom Lane
Date:
Subject: Re: Bug with plpgsql handling of NULL argument of compound type