Re: Index Scan taking long time

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Bryce Ewing <bryce(at)smx(dot)co(dot)nz>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Index Scan taking long time
Date: 2009-06-17 14:23:20
Message-ID: 25686.1245248600@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> Without looking at the explain just yet, it seems to me that you are
> constraining the order of joins to insist that the left joins be done
> first, then the regular joins second, because of your mix of explicit
> and implicit join syntax. The query planner is constrained to run
> explicit joins first, then implicit if I remember correctly.

That isn't true as of recent releases (8.2 and up, I think). It is true
that there are semantic constraints that prevent certain combinations
of inner and outer joins from being rearranged ... but if that applies
here, it would also prevent manual rearrangement, unless the OP decides
that this query doesn't express quite what he meant.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2009-06-17 14:48:15 Re: performance with query
Previous Message Merlin Moncure 2009-06-17 13:08:33 Re: Speeding up a query.