Skip site navigation (1) Skip section navigation (2)

Re: OUTER JOIN performance regression remains in 8.3beta4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: OUTER JOIN performance regression remains in 8.3beta4
Date: 2008-01-07 01:20:10
Message-ID: (view raw or whole thread)
Lists: pgsql-hackerspgsql-patches
"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

Attachment: const-propagation-8.3.patch.gz
Description: application/octet-stream (5.6 KB)

In response to


pgsql-hackers by date

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

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group