aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2018-01-31 16:54:33 -0500
committerBruce Momjian <bruce@momjian.us>2018-01-31 16:54:33 -0500
commit18821280e98ade69c4338d895c57bc22dc67643e (patch)
treed1b37785e60b182df8c769b34cf3da4c60d92770
parentc7be38fa33d2336a70d64dc6b31a3933e2aeb938 (diff)
downloadpostgresql-18821280e98ade69c4338d895c57bc22dc67643e.tar.gz
postgresql-18821280e98ade69c4338d895c57bc22dc67643e.zip
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
-rw-r--r--doc/src/sgml/contrib-spi.sgml4
-rw-r--r--doc/src/sgml/spi.sgml3
2 files changed, 4 insertions, 3 deletions
diff --git a/doc/src/sgml/contrib-spi.sgml b/doc/src/sgml/contrib-spi.sgml
index 3287c18d27d..a88d99d517c 100644
--- a/doc/src/sgml/contrib-spi.sgml
+++ b/doc/src/sgml/contrib-spi.sgml
@@ -10,7 +10,9 @@
<para>
The <application>spi</> module provides several workable examples
- of using SPI and triggers. While these functions are of some value in
+ of using the <link linkend="spi">Server Programming Interface</link>
+ (<acronym>SPI</acronym>) 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 c099fcfad3a..66ab8fbe3d0 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.
</para>
<para>