Re: 7.3.1 New install, large queries are slow - Mailing list pgsql-performance

From Josh Berkus
Subject Re: 7.3.1 New install, large queries are slow
Date
Msg-id web-2316240@davinci.ethosmedia.com
Whole thread Raw
In response to Re: 7.3.1 New install, large queries are slow  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 7.3.1 New install, large queries are slow
List pgsql-performance
Tom,

> The list of explicit JOINs as you have here is a good way to proceed
> *if* you write the JOINs in an appropriate order for implementation.
> I believe the problem with Roman's original query was that he listed
> the JOINs in a bad order.  Unfortunately I didn't keep a copy of that
> message, and the list archives seem to be a day or more behind...
> but at least for these WHERE conditions, it looks like the best bet
> would to join m to b (I'm assuming m.merchid is unique), then to t,
> then to d, then add on the others.

I realize that I've contributed nothing other than bug reports to the
parser design.  But shouldn't Postgres, given a free hand, figure out
the above automatically?    I'd be embarassed if MS could one-up us in
parser planning anywhere, theirs sucks on sub-selects ....

-Josh Berkus

pgsql-performance by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: 7.3.1 New install, large queries are slow
Next
From: Tom Lane
Date:
Subject: Re: 7.3.1 New install, large queries are slow