Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Would it be a good idea to keep removing redundant clauses and rethink
> the preference for clauseful joins, going forward?
No --- it would create an exponential growth in planning time for large
join problems, while not actually buying anything in the typical case.
It's possible that we could do something along the lines of inserting
"dummy" join conditions, to allow particular join paths to be explored,
without generating any clause that actually requires work at runtime.
I'm not convinced this complication is needed though; at least not if
the only thing it's good for is this rather specialized optimization
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-01-08 22:05:23|
|Subject: Re: Proposal - libpq Type System beta-0.8a (was PGparam) |
|Previous:||From: Josh Berkus||Date: 2008-01-08 21:34:46|
|Subject: Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate)|
pgsql-patches by date
|Next:||From: Neil Conway||Date: 2008-01-09 03:14:48|
|Subject: Fix for _outAgg()|
|Previous:||From: Alvaro Herrera||Date: 2008-01-08 21:20:51|
|Subject: Re: OUTER JOIN performance regression remains in 8.3beta4|