summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane2007-03-25 23:27:59 +0000
committerTom Lane2007-03-25 23:27:59 +0000
commitbf8236526be85bc3f061a918dbf49a28bc9bc220 (patch)
tree884ac85f29507b9885d1afc805be8ac65d5f2089 /doc/src
parente85a01df678c9621c225200f1309ca8e682338ff (diff)
Remove the prohibition on executing cursor commands through SPI_execute.
Vadim had included this restriction in the original design of the SPI code, but I'm darned if I can see a reason for it. I left the macro definition of SPI_ERROR_CURSOR in place, so as not to needlessly break any SPI callers that are checking for it, but that code will never actually be returned anymore.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/spi.sgml14
1 files changed, 2 insertions, 12 deletions
diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml
index c7c4304b3a7..14e975b5fc9 100644
--- a/doc/src/sgml/spi.sgml
+++ b/doc/src/sgml/spi.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.54 2007/03/15 23:12:06 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.55 2007/03/25 23:27:59 tgl Exp $ -->
<chapter id="spi">
<title>Server Programming Interface</title>
@@ -555,20 +555,10 @@ typedef struct
</varlistentry>
<varlistentry>
- <term><symbol>SPI_ERROR_CURSOR</symbol></term>
- <listitem>
- <para>
- if <command>DECLARE</>, <command>CLOSE</>, or <command>FETCH</>
- was attempted
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term><symbol>SPI_ERROR_TRANSACTION</symbol></term>
<listitem>
<para>
- if any command involving transaction manipulation was attempted
+ if a transaction manipulation command was attempted
(<command>BEGIN</>,
<command>COMMIT</>,
<command>ROLLBACK</>,