| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Regina Obe <lr(at)pcorp(dot)us>, 'PostgreSQL-development' <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity |
| Date: | 2017-06-03 02:45:03 |
| Message-ID: | 20170603024503.yv6gxvkyx6mtc63m@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2017-05-28 14:03:26 -0400, Tom Lane wrote:
> I think it would be possible to teach eval_const_expressions that
> it must not discard CASE/COALESCE subexpressions that contain SRFs,
> which would preserve the rule that expression simplification doesn't
> change the query semantics.
That sounds like a good idea. Do you want to write up a patch, or
should I? I can, but I'd want to finish the walsender panic and other
signal handling stuff first (mostly waiting for review for now).
> Another possibility is to say that we've broken this situation
> irretrievably and we should start throwing errors for SRFs in
> places where they'd be conditionally evaluated. That's not real
> nice perhaps, but it's better than the way things are right now.
I'd be ok with that too, but I don't really see a strong need so far.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2017-06-03 02:45:46 | Re: logical replication - still unstable after all these months |
| Previous Message | Peter Eisentraut | 2017-06-03 02:13:35 | Re: ALTER SUBSCRIPTION ..SET PUBLICATION <no name> refresh is not throwing error. |