>>> On Mon, Jan 7, 2008 at 9:01 AM, in message
<4781EA7E(dot)EE98(dot)0025(dot)0(at)wicourts(dot)gov>, "Kevin Grittner"
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>>>> On Sun, Jan 6, 2008 at 7:20 PM, in message <29913(dot)1199668810(at)sss(dot)pgh(dot)pa(dot)us>,
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> "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.
>
> Applied and built cleanly. Check found no errors. Startup clean.
>
> Query returns expected rows. Plan looks good. Thanks!
I see this didn't make it into 8.3RC1. Will it be in the 8.3.0 release?
For us, 8.3RC1 performance looks great with the patch,
horrible without.
-Kevin