first execute the view to get totals for all
the jobs in the database and join that result set with my 2 or 3 jobs
that match my filter.
What is it about my view that prevents postgres to effectively use it?
The group bys? the union?
Cheers,
Bastiaan Olij
--
Sent via pgsql-performance maili
Hi Pavel,
That is what I've done in this particular case but there are parts where
I use exist checks in this way that are very cumbersome to write out
like that so I'm hoping there is a way to make the optimizer work with
existence checks in this way.
Cheers,
Bastiaan Olij
On 19/02/
Hi Andy,
I've tried that with the same result. One subquery works beautifully,
two subqueries with an OR and it starts to do a sequential scan...
Thanks,
Bastiaan Olij
On 19/02/13 6:31 PM, Andy wrote:
> Limit the sub-queries to 1, i.e. :
>
> select 1 from Table2 where Tab
ch
is faster?
Kindest Regards,
Bastiaan Olij
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
