Re: join to view over custom aggregate seems like it should be faster

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
Cc: "PostgreSQL Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: join to view over custom aggregate seems like it should be faster
Date: 2007-04-10 18:21:24
Message-ID: 28253.1176229284@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> right, i see that it's actually the 'group by' that does it:
> select a, b from foo join (select a, b from bar group by a,b) q using (a,b);
> is enough to keep it from using the index on a,b from bar. thats too bad...

Some day it'd be nice to be able to reorder grouping/aggregation steps
relative to joins, the way we can now reorder outer joins. Don't hold
your breath though ... I think it'll take some pretty major surgery on
the planner.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Steve 2007-04-10 19:28:48 Question about memory allocations
Previous Message Merlin Moncure 2007-04-10 17:53:02 Re: join to view over custom aggregate seems like it should be faster