Re: Query optimization path - Mailing list pgsql-admin

From Bruno Wolff III
Subject Re: Query optimization path
Date
Msg-id 20030112175351.GA32092@wolff.to
Whole thread Raw
In response to Re: Query optimization path  ("Gaetano Mendola" <mendola@bigfoot.com>)
Responses Case Studio Postgresql  (Vida Luz Arista <vlal@ideay.net.ni>)
List pgsql-admin
On Sun, Jan 12, 2003 at 18:07:14 +0100,
  Gaetano Mendola <mendola@bigfoot.com> wrote:
> "Bruno Wolff III" <bruno@wolff.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.

pgsql-admin by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Query optimization path
Next
From: "sivaramk"
Date:
Subject: Multibyte characters in object names