| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | 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 17:11:35 |
| Message-ID: | 16854.1513962695@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> How about just erroring out?
> Hm, yeah, inserting a FEATURE_NOT_SUPPORTED error might be an
> appropriate amount of effort.
When I looked into this more closely, it turns out that in v10/HEAD
it takes less code to fix it than to throw an error ;-). So I just
fixed it and added some regression tests. But 9.6 blows up somewhere
in the executor, and it didn't seem worth trying to deal with that.
So in 9.4-9.6 I just made the case throw an error.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jernigan, Kevin | 2017-12-22 17:53:15 | Re: AWS Aurora and PG 10 |
| Previous Message | rihad | 2017-12-22 16:58:58 | Re: pg_upgrading to 10.1 corrupts (varchar,varchar) UNIQUE indices |