pgsql: Put back copyObject() call I removed in a fit of brain fade.

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Put back copyObject() call I removed in a fit of brain fade.
Date: 2007-02-25 17:44:01
Message-ID: 20070225174401.3CF7E9FBC79@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Put back copyObject() call I removed in a fit of brain fade. This one
is still needed despite cleanups in setrefs.c, because the point is to
let the inserted Result node compute a different tlist than its input
node does. Per example from Jeremy Drake.

Modified Files:
--------------
pgsql/src/backend/optimizer/plan:
createplan.c (r1.226 -> r1.227)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/createplan.c.diff?r1=1.226&r2=1.227)

Browse pgsql-committers by date

  From Date Subject
Next Message James William Pye 2007-02-25 21:17:54 python - ip: Add 'parameters' arguments(default SETs) and correct
Previous Message James William Pye 2007-02-24 20:36:33 python - rc: Implement remote file interface.