make cross link to "format" more specific

2018-12-07 Thread Jeff Janes
The section on dynamic SQL recommends "format", but the cross link goes to
the top of page 9.4 not the "format" specific 9.4.1.

This is particularly confusing as 9.4 only has one sub-section, so the TOC
at the top of the page only has one entry.  This makes it look more like a
section header itself rather than a TOC.  Leading you to believe you are
already at the specific section you want.

I don't know what to do about the visual misleadingness of single-entry
TOCs in general, but at least we can make this specific cross reference
more specific.

Cheers,

Jeff


string-function-format.patch
Description: Binary data


Re: make cross link to "format" more specific

2018-12-07 Thread Tom Lane
Jeff Janes  writes:
> I don't know what to do about the visual misleadingness of single-entry
> TOCs in general, but at least we can make this specific cross reference
> more specific.

Agreed, done.

regards, tom lane



Broken link in Appendix H.3

2018-12-07 Thread PG Doc comments form
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.


Re: Broken link in Appendix H.3

2018-12-07 Thread Alvaro Herrera
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 Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



Re: Broken link in Appendix H.3

2018-12-07 Thread Alvaro Herrera
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 Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



Re: Broken link in Appendix H.3

2018-12-07 Thread Reece Hart
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.)
>
> --
> Álvaro Herrerahttps://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>


Re: Broken link in Appendix H.3

2018-12-07 Thread James William Pye
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.


Re: Broken link in Appendix H.3

2018-12-07 Thread Peter Eisentraut
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