On Mon, Jan 29, 2018 at 08:58:10PM -0700, David G. Johnston wrote:
> On Mon, Jan 29, 2018 at 8:55 PM, Bruce Momjian <br...@momjian.us> wrote:
>
> On Mon, Jan 29, 2018 at 10:51:59PM -0500, Tom Lane wrote:
> > Bruce Momjian <br...@momjian.us> writes:
> > > How is the attached patch?
> >
> > Maybe also make that text into a hyperlink to the SPI manual chapter?
>
> Yes, that's what I just did in the new patch.
>
>
> ​Your second attachment is the same as the first.
Oops, here is the right one.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
diff --git a/doc/src/sgml/contrib-spi.sgml b/doc/src/sgml/contrib-spi.sgml
new file mode 100644
index 32c7105..844ea16
*** a/doc/src/sgml/contrib-spi.sgml
--- b/doc/src/sgml/contrib-spi.sgml
***************
*** 10,16 ****
<para>
The <application>spi</application> module provides several workable examples
! of using SPI 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
--- 10,18 ----
<para>
The <application>spi</application> module provides several workable examples
! 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
new file mode 100644
index 1044892..0bac342
*** a/doc/src/sgml/spi.sgml
--- b/doc/src/sgml/spi.sgml
***************
*** 42,49 ****
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.
</para>
<para>
--- 42,48 ----
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.
</para>
<para>
