On 23 September 2011 12:31, Ingmar Brouns wrote:
> >
> > In short: if you want to get useful commentary on your problem, you
> > need to provide a more complete picture.
> >
> >regards, tom lane
> >
>
> I've posted the query plans now several times to this list, but they
>
>
> In short: if you want to get useful commentary on your problem, you
> need to provide a more complete picture.
>
> regards, tom lane
>
I've posted the query plans now several times to this list, but they
do not show up, almost as if being caught by a spam filter or
somet
Ingmar Brouns writes:
> What I find strange is that there is a conditionless index scan on
> participates, retrieving all its rows, and then a nested loop over all those
> rows and a materialize node.
Yeah, that indexscan looks pretty odd to me too, but it's likely
explained by the context that y
Hi,
I have a query for which PostgreSQL 9.0.3 and 9.1 rc1 both come up with what
seems to be a very bad plan when materialize is enabled.
The plan with materialize takes 5 seconds to execute, the plan without 7 ms.
Part of the plan with materialization enabled
#effectively loop over all rows in
