doc: in contrib-spi, mention and link to the meaning of SPI

Also remove outdated comment about SPI subtransactions. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.3
ArtyMgn · Jan 31, 2018 · 3b15255 · 3b15255
1 parent 2275796
commit 3b15255
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/doc/src/sgml/contrib-spi.sgml b/doc/src/sgml/contrib-spi.sgml
@@ -10,7 +10,9 @@
 
  <para>
   The <application>spi</application> 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
@@ -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>