Re: [PERFORM]

On Thu, Jun 29, 2017 at 1:11 PM, Yevhenii Kurtov wrote: > Hi Jeff, > > That is just a sample data, we are going live in Jun and I don't have > anything real so far. Right now it's 9.6 and it will be a latest stable > available release on the date that we go live. Trust

Re: [PERFORM]

Pavel Stehule wrote: > 2017-06-29 7:17 GMT+02:00 Yevhenii Kurtov : > > > 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,

Re: [PERFORM]

Hi Jeff, That is just a sample data, we are going live in Jun and I don't have anything real so far. Right now it's 9.6 and it will be a latest stable available release on the date that we go live. On Fri, Jun 30, 2017 at 1:11 AM, Jeff Janes wrote: > On Tue, Jun 27, 2017

Re: [PERFORM]

On Tue, Jun 27, 2017 at 11:47 PM, Yevhenii Kurtov wrote: > Hello, > > We have a query that is run almost each second and it's very important to > squeeze every other ms out of it. The query is: > > SELECT c0."id" FROM "campaign_jobs" AS c0 > WHERE (((c0."status" = $1)

Re: [PERFORM]

2017-06-29 7:17 GMT+02:00 Yevhenii Kurtov : > Hello folks, > > Thank you very much for analysis and suggested - there is a lot to learn > here. I just tried UNION queries and got following error: > > ERROR: FOR UPDATE is not allowed with UNION/INTERSECT/EXCEPT > it