| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Victor Yegorov <vyegorov(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Intersection or zero-column queries |
| Date: | 2017-12-22 15:08:56 |
| Message-ID: | 19206.1513955336@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> writes:
> I noticed I get this behavior in 9.6, but in 9.2 an empty select results in
> a syntax error. Which just got me curious what caused the change, if it
> was deliberate, and if one or the other is more proper behavior.
Yes, it was an intentional change, see
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=1b4f7f93b
There should be something about it in the 9.4 release notes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rihad | 2017-12-22 15:18:10 | Re: pg_upgrading to 10.1 corrupts (varchar,varchar) UNIQUE indices |
| Previous Message | rihad | 2017-12-22 15:07:48 | Re: pg_upgrading to 10.1 corrupts (varchar,varchar) UNIQUE indices |