Re: Proposal: revert behavior of IS NULL on row types - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Proposal: revert behavior of IS NULL on row types
Date
Msg-id CACjxUsOvx+5rHgShDah6HEd1xpVd-QPxfKpm9G17116Q3J6xvA@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: revert behavior of IS NULL on row types  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Mon, Jul 25, 2016 at 8:28 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 7/22/16 7:01 PM, Andrew Gierth wrote:
>> In light of the fact that it is an endless cause of bugs both in pg and
>> potentially to applications, I propose that we cease attempting to
>> conform to the spec's definition of IS NULL in favour of the following
>> rules:
>
> I can't see how we would incompatibly change existing
> standards-conforming behavior merely because users are occasionally
> confused and there are some bugs in corner cases.

+1

Anywhere we have standard-conforming behavior, changing the
semantics of the standard syntax seems insane.  We can create new
syntax for extensions where we are convinced we have a better idea.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: AdvanceXLInsertBuffer vs. WAL segment compressibility
Next
From: Chapman Flack
Date:
Subject: Re: AdvanceXLInsertBuffer vs. WAL segment compressibility