From: Bruce Momjian Date: Wed, 31 Jan 2018 21:54:33 +0000 (-0500) Subject: doc: in contrib-spi, mention and link to the meaning of SPI X-Git-Tag: REL9_6_7~5 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=12db49a83058d8e9269b405d9fe17ea662623e80;p=postgresql doc: in contrib-spi, mention and link to the meaning of SPI Also remove outdated comment about SPI subtransactions. Reported-by: gregory@arenius.com Discussion: https://postgr.es/m/151726276676.1240.10501743959198501067@wrigleys.postgresql.org Backpatch-through: 9.3 --- diff --git a/doc/src/sgml/contrib-spi.sgml b/doc/src/sgml/contrib-spi.sgml index 3287c18d27..a88d99d517 100644 --- a/doc/src/sgml/contrib-spi.sgml +++ b/doc/src/sgml/contrib-spi.sgml @@ -10,7 +10,9 @@ The spi module provides several workable examples - of using SPI and triggers. While these functions are of some value in + of using the Server Programming Interface + (SPI) and triggers. While these functions are of + some value in their own right, they are even more useful as examples to modify for your own purposes. The functions are general enough to be used with any table, but you have to specify table and field names (as described diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml index 9ae7126ae7..2af9c7baea 100644 --- a/doc/src/sgml/spi.sgml +++ b/doc/src/sgml/spi.sgml @@ -42,8 +42,7 @@ have documented error-return conventions. Those conventions only apply for errors detected within the SPI functions themselves, however.) It is possible to recover control after an error by establishing your own - subtransaction surrounding SPI calls that might fail. This is not currently - documented because the mechanisms required are still in flux. + subtransaction surrounding SPI calls that might fail.