Postgres Pro
Downloads
Home   >   mailing lists

Thread: bad url in docs

bad url in docs

From
PG Doc comments form
Date:
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/libpq-ssl.html
Description:

Version 10

33.18. SSL Support

The pointers off to hp.com seem to have gone away on or about 28Aug2018.
They also fall under the heading of HP OpenVMS Systems Doc which may explain
why they've disappeared.

Re: bad url in docs

From
Peter Eisentraut
Date:
On 07/09/2018 00:58, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/10/static/libpq-ssl.html
> Description:
> 
> Version 10
> 
> 33.18. SSL Support
> 
> The pointers off to hp.com seem to have gone away on or about 28Aug2018. 
> They also fall under the heading of HP OpenVMS Systems Doc which may explain
> why they've disappeared.

This has already been fixed in git and will be in the next minor
releases.  Thanks.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: bad url in docs

From
Tom Lane
Date:
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 07/09/2018 00:58, PG Doc comments form wrote:
>> Page: https://www.postgresql.org/docs/10/static/libpq-ssl.html
>> Version 10
>> The pointers off to hp.com seem to have gone away on or about 28Aug2018. 

> This has already been fixed in git and will be in the next minor
> releases.  Thanks.

If you're thinking of 6f1591955, you don't seem to have back-patched
that further than v11.

            regards, tom lane

Re: bad url in docs

From
Peter Eisentraut
Date:
On 07/09/2018 01:27, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>> On 07/09/2018 00:58, PG Doc comments form wrote:
>>> Page: https://www.postgresql.org/docs/10/static/libpq-ssl.html
>>> Version 10
>>> The pointers off to hp.com seem to have gone away on or about 28Aug2018. 
> 
>> This has already been fixed in git and will be in the next minor
>> releases.  Thanks.
> 
> If you're thinking of 6f1591955, you don't seem to have back-patched
> that further than v11.

I have now backpatched this back to 9.3.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services