pgsql-server/ oc/src/sgml/ref/declare.sgml oc/ ...

CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    tgl@postgresql.org    03/03/09 22:53:52

Modified files:
    doc/src/sgml/ref: declare.sgml explain.sgml fetch.sgml move.sgml
                      prepare.sgml
    src/backend/commands: explain.c portalcmds.c
    src/backend/executor: execAmi.c execMain.c spi.c
    src/backend/nodes: copyfuncs.c equalfuncs.c outfuncs.c
                       readfuncs.c
    src/backend/optimizer/path: allpaths.c
    src/backend/optimizer/plan: createplan.c planmain.c planner.c
                                subselect.c
    src/backend/optimizer/prep: prepjointree.c prepunion.c
    src/backend/optimizer/util: clauses.c
    src/backend/parser: analyze.c gram.y parse_clause.c parse_type.c
    src/backend/tcop: postgres.c pquery.c utility.c
    src/backend/utils/mmgr: portalmem.c
    src/include/catalog: catversion.h
    src/include/commands: portalcmds.h
    src/include/executor: executor.h spi.h
    src/include/nodes: nodes.h parsenodes.h
    src/include/optimizer: planmain.h planner.h
    src/include/tcop: pquery.h
    src/include/utils: portal.h

Log message:
    Restructure parsetree representation of DECLARE CURSOR: now it's a
    utility statement (DeclareCursorStmt) with a SELECT query dangling from
    it, rather than a SELECT query with a few unusual fields in it.  Add
    code to determine whether a planned query can safely be run backwards.
    If DECLARE CURSOR specifies SCROLL, ensure that the plan can be run
    backwards by adding a Materialize plan node if it can't.  Without SCROLL,
    you get an error if you try to fetch backwards from a cursor that can't
    handle it.  (There is still some discussion about what the exact
    behavior should be, but this is necessary infrastructure in any case.)
    Along the way, make EXPLAIN DECLARE CURSOR work.