| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Make foo=null a warning by default. |
| Date: | 2018-07-16 15:06:48 |
| Message-ID: | CA+Tgmobgqfc7NJsZbKzzg0ix-97x-qxKDBpHrZYVPaz0uG0URQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 16, 2018 at 3:49 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-16 15:10:27 | Re: Make foo=null a warning by default. |
| Previous Message | Robert Haas | 2018-07-16 15:01:51 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |