"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> There was a serious performance regression in OUTER JOIN planning
> going from 8.2.4 to 8.2.5.  I know Tom came up with some patches to
> mitigate the issues in 8.2.5, but my testing shows that problems
> remain in 8.3beta4.
 
Please try the attached proposed patch.  It seems to fix my simplified
test case, but I'm not sure if there are any additional considerations
involved in your real queries.

This is against CVS HEAD but I think it will apply cleanly to beta4.

Haven't looked closely at how to fix 8.2, yet.

			regards, tom lane

In response to

• OUTER JOIN performance regression remains in 8.3beta4 at 2008-01-04 18:16:13 from Kevin Grittner

Responses

• Re: OUTER JOIN performance regression remains in8.3beta4 at 2008-01-07 15:01:50 from Kevin Grittner
• Re: OUTER JOIN performance regression remains in 8.3beta4 at 2008-01-08 21:11:16 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2008-01-07 02:22:09
	Subject: Re: Index trouble with 8.3b4
Previous:	From: Tom Lane	Date: 2008-01-06 19:44:47
	Subject: Re: BUG #3852: Could not create complex aggregate

pgsql-patches by date

Next:	From: Kevin Grittner	Date: 2008-01-07 15:01:50
	Subject: Re: OUTER JOIN performance regression remains in8.3beta4
Previous:	From: Clodoaldo	Date: 2008-01-06 11:48:44
	Subject: Re: 8.3-beta4, analyze and db owner