diff options
| author | Bruce Momjian | 2018-01-31 21:54:33 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2018-01-31 21:54:33 +0000 |
| commit | 3b15255912af3fa428fbc296d830292ffc8c9803 (patch) | |
| tree | ef96d8efffba3b303cfd63113d28422033297605 | |
| parent | 22757960bb3b2a6fa331bad132998c53b3e744a9 (diff) | |
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
| -rw-r--r-- | doc/src/sgml/contrib-spi.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/spi.sgml | 3 |
2 files changed, 4 insertions, 3 deletions
diff --git a/doc/src/sgml/contrib-spi.sgml b/doc/src/sgml/contrib-spi.sgml index 32c7105cf6..844ea161c4 100644 --- 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 index 10448922b1..0bac342322 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> |