| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "gregory(at)arenius(dot)com" <gregory(at)arenius(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SPI not defined. |
| Date: | 2018-01-29 22:07:06 |
| Message-ID: | CAKFQuwZJcfU+XLjpgEgi446ahVWZUVm=QBUBFGXn2demmLL-qQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Monday, January 29, 2018, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.5/static/contrib-spi.html
> Description:
>
> In the appendix for Additional Supplied Modules there is a module spi. If
> you click through the page for that module it never defines what spi is.
> If
> you search for PostgreSQL spi you get the page that doesn't define it and
> some other information on the PostgreSQL Server Programming Interface,
> which
> I think is a different SPI.
>
No, SPI in that module is indeed "Server Programming Interface".
>
> I would recommend that the module page define
>
the spi acronym.
Seems reasonable.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-01-30 01:16:50 | Re: pg_upgrade docs are confusing if PostgreSQL's versioning system/language isn't known to reader |
| Previous Message | PG Doc comments form | 2018-01-29 21:52:46 | SPI not defined. |