Re: strange IS NULL behaviour - Mailing list pgsql-hackers

From Robert Haas
Subject Re: strange IS NULL behaviour
Date
Msg-id CA+TgmoYyQLULM_kCWE39edzMq6KiNPEzPChGGO2a9a=VAOZP2Q@mail.gmail.com
Whole thread Raw
In response to Re: strange IS NULL behaviour  (Bruce Momjian <bruce@momjian.us>)
Responses Re: strange IS NULL behaviour
List pgsql-hackers
On Wed, Sep 4, 2013 at 9:26 PM, Bruce Momjian <bruce@momjian.us> wrote:
> On Tue, Sep  3, 2013 at 09:32:44PM -0400, Bruce Momjian wrote:
>> In this test, SELECT NULL (which internally would produce SELECT
>> ROW(NULL)), returns TRUE, while SELECT ROW(NULL) and further nesting
>> returns false.
>>
>> This has made me adjust my goal and change it so SELECT ROW(NULL) IS
>> NULL returns true, and any further nesting returns false.
>>
>> Attached is a patch which accomplishes this, and a documentation update.
>
> I have not heard any feedback on this patch, so I would like to apply it
> to give us a nested ROW/IS NULL API we can document.  It would have to
> be marked in the release notes as a backward incompatibility.

I don't have time to look at this in detail right now, but I think
that's considerably premature.  I'm not convinced that we understand
all of the problems in this area are yet, let alone the solutions.
And I notice that you haven't substantively responded to some of Tom's
concerns.

So -1 from me.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: logical changeset generation v5
Next
From: Andres Freund
Date:
Subject: Re: lcr v5 - introduction of InvalidCommandId