| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Subject: | Re: Bug with plpgsql handling of NULL argument of compound type |
| Date: | 2016-07-22 19:46:27 |
| Message-ID: | 20160722194627.GA183946@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-07-22 20:22:49 | Re: Bug with plpgsql handling of NULL argument of compound type |
| Previous Message | Tom Lane | 2016-07-22 19:42:26 | Re: fixes for the Danish locale |