pgsql: Fix a performance regression in 8.2: optimization of MIN/MAX into

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix a performance regression in 8.2: optimization of MIN/MAX into
Date: 2007-02-06 06:50:26
Message-ID: 20070206065026.35EBD9FB1C6@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix a performance regression in 8.2: optimization of MIN/MAX into indexscans
had stopped working for tables buried inside views or sub-selects. This is
because I had gotten rid of the simplify_jointree() preprocessing step, and
optimize_minmax_aggregates() wasn't smart enough to deal with a non-canonical
FromExpr. Per gripe from Bill Howe.

Modified Files:
--------------
pgsql/src/backend/optimizer/plan:
planagg.c (r1.25 -> r1.26)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planagg.c.diff?r1=1.25&r2=1.26)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-02-06 06:50:33 pgsql: Fix a performance regression in 8.2: optimization of MIN/MAX into
Previous Message Tom Lane 2007-02-06 04:38:31 pgsql: Docs updates for cross-type hashing.