pgsql: This patch moves some code for preprocessing FOR UPDATE from - Mailing list pgsql-committers

From neilc@svr1.postgresql.org (Neil Conway)
Subject pgsql: This patch moves some code for preprocessing FOR UPDATE from
Date
Msg-id 20050317234541.941CC565AE@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
This patch moves some code for preprocessing FOR UPDATE from
grouping_planner() to preprocess_targetlist(), according to a comment
in grouping_planner(). I think the refactoring makes sense, and moves
some extraneous details out of grouping_planner().

Modified Files:
--------------
    pgsql/src/backend/optimizer/plan:
        planner.c (r1.179 -> r1.180)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planner.c.diff?r1=1.179&r2=1.180)
    pgsql/src/backend/optimizer/prep:
        preptlist.c (r1.72 -> r1.73)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/prep/preptlist.c.diff?r1=1.72&r2=1.73)
    pgsql/src/include/optimizer:
        prep.h (r1.47 -> r1.48)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/prep.h.diff?r1=1.47&r2=1.48)

pgsql-committers by date:

Previous
From: cmaj@pgfoundry.org (User Cmaj)
Date:
Subject: pgaccess - pgaccess: Forcing wizard for new database creation.
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Treat EPERM as a non-error case when checking to see if old