I've had this small patch in my local tree for a while.  It documents
new commands which may make an SPI call fail.

-- 
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
Maybe there's lots of data loss but the records of data loss are also lost.
(Lincoln Yeoh)
Index: doc/src/sgml/spi.sgml
===================================================================
RCS file: /home/alvherre/cvs/pgsql/doc/src/sgml/spi.sgml,v
retrieving revision 1.41
diff -c -r1.41 spi.sgml
*** doc/src/sgml/spi.sgml       2 May 2005 00:37:06 -0000       1.41
--- doc/src/sgml/spi.sgml       27 Jul 2005 15:44:26 -0000
***************
*** 537,544 ****
       <term><symbol>SPI_ERROR_TRANSACTION</symbol></term>
       <listitem>
        <para>
!        if <command>BEGIN</>, <command>COMMIT</>, or
!        <command>ROLLBACK</> was attempted
        </para>
       </listitem>
      </varlistentry>
--- 537,551 ----
       <term><symbol>SPI_ERROR_TRANSACTION</symbol></term>
       <listitem>
        <para>
!          if any command involving transaction manipulation was attempted
!          (<command>BEGIN</>,
!          <command>COMMIT</>,
!          <command>ROLLBACK</>,
!          <command>SAVEPOINT</>,
!          <command>PREPARE TRANSACTION</>,
!          <command>COMMIT PREPARED</>,
!          <command>ROLLBACK PREPARED</>,
!          or any variant thereof)
        </para>
       </listitem>
      </varlistentry>
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to