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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
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 20:22:49
Message-ID: 10278.1469218969@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On this topic, see also
> https://www.postgresql.org/message-id/20160708024746.1410.57282@wrigleys.postgresql.org

I'd forgotten about that thread :-( ... but on looking at it, it's very
relevant indeed. See my followup there.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-07-22 20:53:00 Re: Rethinking TupleTableSlot deforming
Previous Message Alvaro Herrera 2016-07-22 19:46:27 Re: Bug with plpgsql handling of NULL argument of compound type