Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1egMYw-0003Me-Gd
	for pgsql-docs@arkaria.postgresql.org; Tue, 30 Jan 2018 03:26:22 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1egMYv-0004Rr-Fw
	for pgsql-docs@arkaria.postgresql.org; Tue, 30 Jan 2018 03:26:21 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <bruce@momjian.us>)
	id 1egMYv-0004Rc-74
	for pgsql-docs@lists.postgresql.org; Tue, 30 Jan 2018 03:26:21 +0000
Received: from momjian.us ([72.94.173.45])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <bruce@momjian.us>)
	id 1egMYs-00017x-GD
	for pgsql-docs@lists.postgresql.org; Tue, 30 Jan 2018 03:26:19 +0000
Received: from bruce by momjian.us with local (Exim 4.84_2)
	(envelope-from <bruce@momjian.us>)
	id 1egMYq-0007fX-EQ; Mon, 29 Jan 2018 22:26:16 -0500
Date: Mon, 29 Jan 2018 22:26:16 -0500
From: Bruce Momjian <bruce@momjian.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: "gregory@arenius.com" <gregory@arenius.com>,
	"pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Subject: Re: SPI not defined.
Message-ID: <20180130032616.GA23631@momjian.us>
References: <151726276676.1240.10501743959198501067@wrigleys.postgresql.org>
 <CAKFQuwZJcfU+XLjpgEgi446ahVWZUVm=QBUBFGXn2demmLL-qQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="tKW2IUtsqtDRztdT"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAKFQuwZJcfU+XLjpgEgi446ahVWZUVm=QBUBFGXn2demmLL-qQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk


--tKW2IUtsqtDRztdT
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

On Mon, Jan 29, 2018 at 03:07:06PM -0700, David G. Johnston wrote:
> On Monday, January 29, 2018, PG Doc comments form <noreply@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  <bruce@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 +

--tKW2IUtsqtDRztdT
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="spi.diff"

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

--tKW2IUtsqtDRztdT--