Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gVMcT-0005GY-IR for pgsql-docs@arkaria.postgresql.org; Fri, 07 Dec 2018 20:21:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gVMcS-0001pi-9H for pgsql-docs@arkaria.postgresql.org; Fri, 07 Dec 2018 20:21:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gVJr5-0001sB-EV for pgsql-docs@lists.postgresql.org; Fri, 07 Dec 2018 17:23:59 +0000 Received: from mail-oi1-x244.google.com ([2607:f8b0:4864:20::244]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gVJr1-0004ef-HS for pgsql-docs@lists.postgresql.org; Fri, 07 Dec 2018 17:23:58 +0000 Received: by mail-oi1-x244.google.com with SMTP id h25so3993457oig.1 for ; Fri, 07 Dec 2018 09:23:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=harts-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4l/41oyJFEje3xw4cmzzngAMgiskbYHkAzSprkqvNbI=; b=vA+825M+LKFbfOvD0S/N5PgT8bSvz5lQxQdylKqE7fpaq11Rbd3ew+4FVwgslYI6QQ AhfcZGLLs/U0sbfRAGDg5UVEwTHyzzfvzOMErUUt8d7k8blU8avUoHuyBtfoH0O5X1Pn Ch0QmfaqdjAt8adxcX7KIAcCZNP+MSQGvGuibqYkiQYZvT1MCN4cW6a7fys5py3RWHGo 31akdNoKdm3jwJAb1d2ofGVKzfkJB+K0oKVQUKO51/wTBzM/gfsS6XOwIJK1V61FLNdH pD7jg3WA9RETjZ8nh83gSSiSz965mKDqcjKeIAQenKsZPMNfOO8/eDnawfFG6urgQiHu POdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4l/41oyJFEje3xw4cmzzngAMgiskbYHkAzSprkqvNbI=; b=a8HHrNul0jkaSAJXWvN8mUBXCBWsL/gcq4aWPrgBYBLVxl6DR/DtC1oq/F3SQPECoF CvNZUTIKVNg1c08PS87DHwVo8R/5XzCKHQKFqXe9L38C2p0VieXhFV/+qkv/ytpqxjHv VXB4VZfBq+muedZmkRJ8Yt8cZh2NviyyxCzvmm2XKMmuiJXl7GmVMdxhShFjVZuoButD lm6bbNWKf9LTxt3h9mgngfPl7krasOJfaNDKvamdEzXVD3nU9qVlxUMU5j/kubscD+Ta jUYRSCTOzxQ9mpD89lMgp9c31etj8RTGdl2eA+FCf/SsxnrlBOjbvryI5S8Wu64b2Ieq 3FHA== X-Gm-Message-State: AA+aEWapGwyn03HULBIcu1w2mJplpdOA75Ea17S8vhP7Bbu082ho3Qjx YIbWDaer6d7AeXnJr0IN5LJPiZGP7IIvnxqEfMa0Qg== X-Google-Smtp-Source: AFSGD/V30xdY82qV4KBtDvWCZMepxsydu37RSuM4/8i8DD/9Ba4AeyT7qwh74OW3TYvxramroExZFB+xy6QXFYOzA7M= X-Received: by 2002:aca:f341:: with SMTP id r62mr1792089oih.271.1544203433204; Fri, 07 Dec 2018 09:23:53 -0800 (PST) MIME-Version: 1.0 References: <20181207170724.uuwplyidrgfatl7o@alvherre.pgsql> <20181207171636.mrtb4vfan5rcdge6@alvherre.pgsql> In-Reply-To: <20181207171636.mrtb4vfan5rcdge6@alvherre.pgsql> From: Reece Hart Date: Fri, 7 Dec 2018 09:23:26 -0800 Message-ID: Subject: Re: Broken link in Appendix H.3 To: alvherre@2ndquadrant.com Cc: pgsql-docs@lists.postgresql.org, james.pye@gmail.com Content-Type: multipart/alternative; boundary="00000000000018f8c9057c71e1a1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000018f8c9057c71e1a1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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, the link shown is > > > http://python.projects.postgresql.org/backend/, which redirects to > > > http://python.projects.pgfoundry.org/backend/ and returns 404. I > don't know > > > what the correct link should be, if any. > > > > I think PL/Py doesn't exist anymore. > > Some digging turns up that James Pye renamed it to pg-python and moved > to github https://github.com/python-postgres/be but last commit was 4 > years ago to add 9.3 support, so I guess we should just remove it. > > (Meanwhile his Python driver continues to live.) > > -- > =C3=81lvaro Herrera https://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services > --00000000000018f8c9057c71e1a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Removing the PL/Py entry sounds right to = me.=C2=A0

How about adding plv8 (https://github.com/plv8/plv8) at th= e same time?

On Fri, Dec 7, 2018 at 9:16 AM Alvaro Herrera <alvherre@2ndquadrant.com> wr= ote:
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 websit= e:
> >
> > 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, the link shown is
> > http://python.projects.postgresql.org/backen= d/, which redirects to
> > http://python.projects.pgfoundry.org/backend/= and returns 404. I don't know
> > what the correct link should be, if any.
>
> I think PL/Py doesn't exist anymore.

Some digging turns up that James Pye renamed it to pg-python and moved
to github https://github.com/python-postgres/be but last co= mmit was 4
years ago to add 9.3 support, so I guess we should just remove it.

(Meanwhile his Python driver continues to live.)

--
=C3=81lvaro Herrera=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--00000000000018f8c9057c71e1a1--