Re: Postgresql 8.1.4 - performance issues for select on - Mailing list pgsql-performance

From Tom Lane
Subject Re: Postgresql 8.1.4 - performance issues for select on
Date
Msg-id 2694.1161212717@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgresql 8.1.4 - performance issues for select on  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Postgresql 8.1.4 - performance issues for select on  (Ioana Danes <ioanasoftware@yahoo.ca>)
List pgsql-performance
Jeff Davis <pgsql@j-davis.com> writes:
> If PostgreSQL could sort the result of a union by merging the results of
> two index scans, I think the problem would be solved. Is there something
> preventing this, or is it just something that needs to be added to the
> planner?

It's something on the wish-list.  Personally I'd be inclined to try to
rewrite the query as a plain MAX() across rewritten per-table indexed
queries, rather than worry about mergesort or anything like that.
There wasn't any very good way to incorporate that idea when planagg.c
was first written, but now that the planner has an explicit notion of
"append relations" it might be relatively straightforward.

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: index growth problem
Next
From: Jeff Davis
Date:
Subject: Re: Postgresql 8.1.4 - performance issues for select on