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 05:10:28 |
Message-ID: | 20030616001028.Q66185@flake.decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Jun 12, 2003 at 06:48:27AM +0200, pginfo wrote:
> Many thanks Tom,
> the doc do not contain solution for this case, but the idea to
> change the join order was excelent and all is working fine at the moment.
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?
IMHO I think it's bad that using the ANSI syntax forces join order; it
would be much better to come up with a custom syntax for this like
everyone else does. But I'm sure people won't want to change the
existing behavior, so special syntax to do the opposite is almost as
good.
--
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 05:17:40 | Re: tweaking costs to favor nestloop |
Previous Message | Tomaz Borstnar | 2003-06-15 23:21:34 | Re: any way to use indexscan to get last X values |