Re: Limit + group + join - Mailing list pgsql-performance

From Tom Lane
Subject Re: Limit + group + join
Date
Msg-id 9501.1125071193@sss.pgh.pa.us
Whole thread Raw
In response to Re: Limit + group + join  (Mark Kirkwood <markir@paradise.net.nz>)
Responses Re: Limit + group + join  (Mark Kirkwood <markir@paradise.net.nz>)
Re: Limit + group + join  (Mark Kirkwood <markir@paradise.net.nz>)
Re: Limit + group + join  (Greg Stark <gsstark@mit.edu>)
List pgsql-performance
Mark Kirkwood <markir@paradise.net.nz> writes:
> What is interesting is why this plan is being rejected...

Which PG version are you using exactly?  That mistake looks like an
artifact of the 8.0 "fuzzy plan cost" patch, which we fixed recently:
http://archives.postgresql.org/pgsql-committers/2005-07/msg00474.php

But Tobias wasn't happy with 7.4 either, so I'm not sure that the fuzzy
cost issue explains his results.

As far as the "desc" point goes, the problem is that mergejoins aren't
capable of dealing with backward sort order, so a merge plan isn't
considered for that case (or at least, it would have to have a sort
after it, which pretty much defeats the point for a fast-start plan).
I have some ideas about fixing this but it won't happen before 8.2.

            regards, tom lane

pgsql-performance by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: difference in plan between 8.0 and 8.1?
Next
From: Frank Wiles
Date:
Subject: Re: Sending a select to multiple servers.