From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Query optimization path |
Date: | 2003-01-12 17:53:51 |
Message-ID: | 20030112175351.GA32092@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sun, Jan 12, 2003 at 18:07:14 +0100,
Gaetano Mendola <mendola(at)bigfoot(dot)com> wrote:
> "Bruno Wolff III" <bruno(at)wolff(dot)to> wrote in message
>
> > Using "JOIN" fixes the order that tables are joined in. If you are
> > just doing inner joins, then you probably don't want to use the "JOIN"
> > keyword. The exception being when there are so many tables being joined
> > that you want to manually specify at least some of the join ordering in
> > order to help out the planner.
>
> And where is written this behavior ? Is it SQL standard ?
The SQL standard isn't going to address performance, just results.
Look in section 10.3 of the User's Guide. This is under Performance Tips
and Controlling the Planner with Explicit JOIN Clauses.
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Abernethy IV | 2003-01-13 01:53:52 | Re: Encrypted Passwords |
Previous Message | Stephan Szabo | 2003-01-12 17:28:37 | Re: Query optimization path |