On 3/6/10 5:45 PM, Tom Lane wrote:
> The reason for the behavioral change is that plpgsql, which formerly
> had really crummy tuple conversion logic with a whole bunch of other
> deficiencies besides this one, now shares the logic used by
> ConvertRowtypeExpr.
Oh, yes, of course. Should have thou
Accidentally replied to Tom directly. Sending to the list now.
On Sun, Mar 7, 2010 at 9:08 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Fri, Mar 5, 2010 at 5:32 PM, Tom Lane wrote:
>>> It's arguably a bug, but since we lack consensus on whether NULL and
>>> ROW(NULL,NULL,...) are the same t
Robert Haas writes:
> On Fri, Mar 5, 2010 at 5:32 PM, Tom Lane wrote:
>> It's arguably a bug, but since we lack consensus on whether NULL and
>> ROW(NULL,NULL,...) are the same thing, it's difficult to make a
>> bulletproof case either way.
> Have we or can we somehow document why this happens?
