| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Yevhenii Kurtov <yevhenii(dot)kurtov(at)gmail(dot)com>, Brad DeJong <Brad(dot)Dejong(at)infor(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: |
| Date: | 2017-06-29 21:28:23 |
| Message-ID: | 20170629212823.57u4eibfc6sn3hey@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Pavel Stehule wrote:
> 2017-06-29 7:17 GMT+02:00 Yevhenii Kurtov <yevhenii(dot)kurtov(at)gmail(dot)com>:
>
> > I just tried UNION queries and got following error:
> >
> > ERROR: FOR UPDATE is not allowed with UNION/INTERSECT/EXCEPT
>
> it is sad :(
I think we could lift this restriction for UNION ALL, but UNION sounds
difficult.
BTW I wonder how much of the original problem is caused by using a
prepared query. I understand the desire to avoid repeated planning
work, but I think in this case it may be working against you.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2017-06-30 03:09:28 | Re: |
| Previous Message | Yevhenii Kurtov | 2017-06-29 19:11:43 | Re: |