On Mon, Jan 29, 2018 at 03:07:06PM -0700, David G. Johnston wrote:
> On Monday, January 29, 2018, PG Doc comments form <nore...@postgresql.org>
> No, SPI in that module is indeed "Server Programming Interface".
>
> I would recommend that the module page define
>
> the spi acronym.
>
> Seems reasonable.
How is the attached patch?
--
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..2dc2d92
*** 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,17 ----
<para>
The <application>spi</application> module provides several workable examples
! of using the Server Programming Interface (<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
