summaryrefslogtreecommitdiff
path: root/doc/src
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
commit19eb7f84e75f592c7a7134d2d02105a3d44ff7e7 (patch)
tree06c628297a0b85ad7abb5da8489e442d4d051771 /doc/src
parenta9fd6c321672c14940461ee47c52434bcf2ecdf9 (diff)
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
Diffstat (limited to 'doc/src')
-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 86be87c0fdb..9ce1270d376 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>