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

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Put back copyObject() call I removed in a fit of brain fade.
Date
Msg-id 20070225174401.3CF7E9FBC79@postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: jwp@pgfoundry.org (James William Pye)
Date:
Subject: python - rc: Implement remote file interface.
Next
From: jwp@pgfoundry.org (James William Pye)
Date:
Subject: python - ip: Add 'parameters' arguments(default SETs) and correct