From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: left join performance problem |
Date: | 2003-06-16 22:41:05 |
Message-ID: | 20030616224105.GL40542@flake.decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Jun 16, 2003 at 09:26:13AM -0400, Tom Lane wrote:
> "Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> > On Mon, Jun 16, 2003 at 01:28:26AM -0400, Tom Lane wrote:
> >> "Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> > Any chance of getting a TODO added that would provide the option of
> > having the optimizer pick join order when you're using the ANSI join
> > syntax?
> >>
> >> No ... because it's already DONE.
>
> > DOH, I forgot about the subselect trick. Nevermind.
>
> No, I wasn't talking about that. See
> http://developer.postgresql.org/docs/postgres/explicit-joins.html
> for the way it works in CVS tip.
Ahh, cool. BTW, I think it should be prominently mentioned in
http://developer.postgresql.org/docs/postgres/sql-select.html#SQL-FROM
that ANSI join syntax can force join order, since most DBA's unfamiliar
with pgsql probably won't be expecting that.
--
Jim C. Nasby (aka Decibel!) jim(at)nasby(dot)net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2003-06-16 22:45:27 | Re: sequential scans on few columns tables |
Previous Message | Tom Lane | 2003-06-16 22:39:24 | Re: Partial index where clause not filtering through |