Re: Make foo=null a warning by default. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Make foo=null a warning by default.
Date
Msg-id CA+Tgmobgqfc7NJsZbKzzg0ix-97x-qxKDBpHrZYVPaz0uG0URQ@mail.gmail.com
Whole thread Raw
In response to Re: Make foo=null a warning by default.  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Mon, Jul 16, 2018 at 3:49 AM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> I don't agree with changing the default to 'warn'. "foo = NULL" is perfectly
> legal SQL, even if it's not very useful in practice.

+1.  I think that will probably generate lots of annoying warnings in
server logs compared to the value it adds.  I don't object to having
an optional feature to generate warnings, but I think it should be
something a particular user needs to activate, not something we enable
by default.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] advanced partition matching algorithm forpartition-wise join
Next
From: Tom Lane
Date:
Subject: Re: Make foo=null a warning by default.