pgsql: Adjust grammar for plpgsql's OPEN command so that a cursor can be - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Adjust grammar for plpgsql's OPEN command so that a cursor can be
Date
Msg-id 20050405180546.799ED53319@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Adjust grammar for plpgsql's OPEN command so that a cursor can be
OPENed on non-SELECT commands such as EXPLAIN or SHOW (anything that
returns tuples is allowed).  This flexibility already existed for
bound cursors, but OPEN was artificially restricting what it would
take.  Per a gripe some months back.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        plpgsql.sgml (r1.63 -> r1.64)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plpgsql.sgml.diff?r1=1.63&r2=1.64)
    pgsql/src/pl/plpgsql/src:
        gram.y (r1.67 -> r1.68)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.67&r2=1.68)

pgsql-committers by date:

Previous
From: andrewsn@pgfoundry.org (User Andrewsn)
Date:
Subject: newsysviews - newsysview: add index views.
Next
From: decibel@pgfoundry.org (User Decibel)
Date:
Subject: newsysviews - newsysview: pg_database.template should be a boolean