From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql-server/src/backend/optimizer/plan create ... |
Date: | 2004-02-29 17:36:06 |
Message-ID: | 20040229173606.0A735D1E925@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl(at)svr1(dot)postgresql(dot)org 04/02/29 13:36:05
Modified files:
src/backend/optimizer/plan: createplan.c
Log message:
make_sort_from_pathkeys()'s method for choosing which of several
equivalent sort expressions to use was broken: you can't just look
at the relation membership, you have to actually grovel over the
individual Vars in each expression. I think this did work when it
was written, but it was broken by subsequent optimizations that made
join relations not propagate every single input variable upward.
Must find the Var that got propagated, not choose one at random.
Per bug report from Daniel O'Neill.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-29 17:36:48 | pgsql-server/src/backend/optimizer/plan Tag: R ... |
Previous Message | Neil Conway | 2004-02-29 15:45:53 | pgsql-server/doc/src/sgml func.sgml |