pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedBroken link in Appendix H.3
7+ messages / 5 participants
[nested] [flat]
* Broken link in Appendix H.3
@ 2018-12-07 16:41 PG Doc comments form <noreply@postgresql.org>
2018-12-07 17:07 ` Re: Broken link in Appendix H.3 Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-08 07:24 ` Re: Broken link in Appendix H.3 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 2 replies; 7+ messages in thread
From: PG Doc comments form @ 2018-12-07 16:41 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: reece@harts.net
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.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Broken link in Appendix H.3
2018-12-07 16:41 Broken link in Appendix H.3 PG Doc comments form <noreply@postgresql.org>
@ 2018-12-07 17:07 ` Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-07 17:16 ` Re: Broken link in Appendix H.3 Alvaro Herrera <alvherre@2ndquadrant.com>
1 sibling, 1 reply; 7+ messages in thread
From: Alvaro Herrera @ 2018-12-07 17:07 UTC (permalink / raw)
To: reece@harts.net; pgsql-docs@lists.postgresql.org
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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Broken link in Appendix H.3
2018-12-07 16:41 Broken link in Appendix H.3 PG Doc comments form <noreply@postgresql.org>
2018-12-07 17:07 ` Re: Broken link in Appendix H.3 Alvaro Herrera <alvherre@2ndquadrant.com>
@ 2018-12-07 17:16 ` Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-07 17:23 ` Re: Broken link in Appendix H.3 Reece Hart <reece@harts.net>
0 siblings, 1 reply; 7+ messages in thread
From: Alvaro Herrera @ 2018-12-07 17:16 UTC (permalink / raw)
To: reece@harts.net; pgsql-docs@lists.postgresql.org; +Cc: james.pye@gmail.com
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.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Broken link in Appendix H.3
2018-12-07 16:41 Broken link in Appendix H.3 PG Doc comments form <noreply@postgresql.org>
2018-12-07 17:07 ` Re: Broken link in Appendix H.3 Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-07 17:16 ` Re: Broken link in Appendix H.3 Alvaro Herrera <alvherre@2ndquadrant.com>
@ 2018-12-07 17:23 ` Reece Hart <reece@harts.net>
2018-12-07 20:03 ` Re: Broken link in Appendix H.3 James William Pye <james.pye@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Reece Hart @ 2018-12-07 17:23 UTC (permalink / raw)
To: alvherre@2ndquadrant.com; +Cc: pgsql-docs@lists.postgresql.org; james.pye@gmail.com
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 <alvherre@2ndquadrant.com>
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.)
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Broken link in Appendix H.3
2018-12-07 16:41 Broken link in Appendix H.3 PG Doc comments form <noreply@postgresql.org>
2018-12-07 17:07 ` Re: Broken link in Appendix H.3 Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-07 17:16 ` Re: Broken link in Appendix H.3 Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-07 17:23 ` Re: Broken link in Appendix H.3 Reece Hart <reece@harts.net>
@ 2018-12-07 20:03 ` James William Pye <james.pye@gmail.com>
0 siblings, 0 replies; 7+ messages in thread
From: James William Pye @ 2018-12-07 20:03 UTC (permalink / raw)
To: reece@harts.net; +Cc: alvherre@2ndquadrant.com; pgsql-docs@lists.postgresql.org
On Fri, Dec 7, 2018 at 10:23 AM Reece Hart <reece@harts.net> 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.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Broken link in Appendix H.3
2018-12-07 16:41 Broken link in Appendix H.3 PG Doc comments form <noreply@postgresql.org>
@ 2018-12-08 07:24 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2018-12-09 15:46 ` Re: Broken link in Appendix H.3 Reece Hart <reece@harts.net>
1 sibling, 1 reply; 7+ messages in thread
From: Peter Eisentraut @ 2018-12-08 07:24 UTC (permalink / raw)
To: reece@harts.net, pgsql-docs@lists.postgresql.org, PG Doc comments form <noreply@postgresql.org>
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. 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.
This was already removed in the PostgreSQL 10 documentation.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Broken link in Appendix H.3
2018-12-07 16:41 Broken link in Appendix H.3 PG Doc comments form <noreply@postgresql.org>
2018-12-08 07:24 ` Re: Broken link in Appendix H.3 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
@ 2018-12-09 15:46 ` Reece Hart <reece@harts.net>
0 siblings, 0 replies; 7+ messages in thread
From: Reece Hart @ 2018-12-09 15:46 UTC (permalink / raw)
To: peter.eisentraut@2ndquadrant.com; +Cc: pgsql-docs@lists.postgresql.org; noreply@postgresql.org
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.eisentraut@2ndquadrant.com> wrote:
> 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. 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.
>
> This was already removed in the PostgreSQL 10 documentation.
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2018-12-09 15:46 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-12-07 16:41 Broken link in Appendix H.3 PG Doc comments form <noreply@postgresql.org>
2018-12-07 17:07 ` Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-07 17:16 ` Alvaro Herrera <alvherre@2ndquadrant.com>
2018-12-07 17:23 ` Reece Hart <reece@harts.net>
2018-12-07 20:03 ` James William Pye <james.pye@gmail.com>
2018-12-08 07:24 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2018-12-09 15:46 ` Reece Hart <reece@harts.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox