I apologize for the goose chase, guys. I *meant* to be looking at the
current docs.
(dons paper bag)
On Fri, Dec 7, 2018 at 11:24 PM Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> wrote:
> On 07/12/2018 17:41, PG Doc comments form wrote:
> > The following documentation comment has been log
On 07/12/2018 17:41, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/external-pl.html
> Description:
>
> At https://www.postgresql.org/docs/9.4/external-pl.html, the link to PL/Py
> is broken. Specific
Removing the PL/Py entry sounds right to me.
How about adding plv8 (https://github.com/plv8/plv8) at the same time?
On Fri, Dec 7, 2018 at 9:16 AM Alvaro Herrera
wrote:
> On 2018-Dec-07, Alvaro Herrera wrote:
>
> > On 2018-Dec-07, PG Doc comments form wrote:
> >
> > > The following documentatio
On Fri, Dec 7, 2018 at 10:23 AM Reece Hart wrote:
> Removing the PL/Py entry sounds right to me.
>
Yes, removal is appropriate. While I may satisfy a random urge to maintain
it in the future, I'd prefer to not encourage it as a solution.
On 2018-Dec-07, Alvaro Herrera wrote:
> On 2018-Dec-07, PG Doc comments form wrote:
>
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/9.4/external-pl.html
> > Description:
> >
> > At https://www.postgresql.org/docs/9.4/extern
On 2018-Dec-07, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/external-pl.html
> Description:
>
> At https://www.postgresql.org/docs/9.4/external-pl.html, the link to PL/Py
> is broken. Specifically
