File tree Expand file tree Collapse file tree 2 files changed +4
-3
lines changed Expand file tree Collapse file tree 2 files changed +4
-3
lines changed Original file line number Diff line number Diff line change 1010
1111 <para>
1212 The <application>spi</application> module provides several workable examples
13- of using SPI and triggers. While these functions are of some value in
13+ of using the <link linkend="spi">Server Programming Interface</link>
14+ (<acronym>SPI</acronym>) and triggers. While these functions are of
15+ some value in
1416 their own right, they are even more useful as examples to modify for
1517 your own purposes. The functions are general enough to be used
1618 with any table, but you have to specify table and field names (as described
Original file line number Diff line number Diff line change 4242 have documented error-return conventions. Those conventions only apply
4343 for errors detected within the SPI functions themselves, however.)
4444 It is possible to recover control after an error by establishing your own
45- subtransaction surrounding SPI calls that might fail. This is not currently
46- documented because the mechanisms required are still in flux.
45+ subtransaction surrounding SPI calls that might fail.
4746 </para>
4847
4948 <para>
You can’t perform that action at this time.
0 commit comments