| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: revert behavior of IS NULL on row types |
| Date: | 2016-07-26 13:24:10 |
| Message-ID: | CACjxUsOvx+5rHgShDah6HEd1xpVd-QPxfKpm9G17116Q3J6xvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 25, 2016 at 8:28 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2016-07-26 13:31:50 | Re: AdvanceXLInsertBuffer vs. WAL segment compressibility |
| Previous Message | Amit Kapila | 2016-07-26 12:48:46 | Re: AdvanceXLInsertBuffer vs. WAL segment compressibility |