pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedBroken link in JSON Types documentation
5+ messages / 3 participants
[nested] [flat]
* Broken link in JSON Types documentation
@ 2019-01-02 20:01 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 5+ messages in thread
From: PG Doc comments form @ 2019-01-02 20:01 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: elisabeth314@gmail.com
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.4/datatype-json.html
Description:
https://www.postgresql.org/docs/9.4/datatype-json.html
Links to http://rfc7159.net/rfc7159. I get a 403 error for both
http://rfc7159.net/rfc7159 and http://rfc7159.net/.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Broken link in JSON Types documentation
@ 2019-01-02 23:11 Tom Lane <tgl@sss.pgh.pa.us>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2019-01-02 23:11 UTC (permalink / raw)
To: elisabeth314@gmail.com; +Cc: pgsql-docs@lists.postgresql.org
=?utf-8?q?PG_Doc_comments_form?= <noreply@postgresql.org> writes:
> https://www.postgresql.org/docs/9.4/datatype-json.html
> Links to http://rfc7159.net/rfc7159. I get a 403 error for both
> http://rfc7159.net/rfc7159 and http://rfc7159.net/.
In PG v10 and up this link goes to https://tools.ietf.org/html/rfc7159.
Evidently whoever updated it didn't bother to back-patch into old
branches.
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Broken link in JSON Types documentation
@ 2019-01-04 13:03 Michael Paquier <michael@paquier.xyz>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Michael Paquier @ 2019-01-04 13:03 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: elisabeth314@gmail.com; pgsql-docs@lists.postgresql.org
On Wed, Jan 02, 2019 at 06:11:55PM -0500, Tom Lane wrote:
> In PG v10 and up this link goes to https://tools.ietf.org/html/rfc7159.
> Evidently whoever updated it didn't bother to back-patch into old
> branches.
I don't think that really cool to have user-facing documentation which
goes to the void on supported branches, especially if there is an
adequate replacement. Tom, do you think that this is worth updating?
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Broken link in JSON Types documentation
@ 2019-01-04 14:50 Tom Lane <tgl@sss.pgh.pa.us>
parent: Michael Paquier <michael@paquier.xyz>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2019-01-04 14:50 UTC (permalink / raw)
To: Michael Paquier <michael@paquier.xyz>; +Cc: elisabeth314@gmail.com; pgsql-docs@lists.postgresql.org
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, Jan 02, 2019 at 06:11:55PM -0500, Tom Lane wrote:
>> In PG v10 and up this link goes to https://tools.ietf.org/html/rfc7159.
>> Evidently whoever updated it didn't bother to back-patch into old
>> branches.
> I don't think that really cool to have user-facing documentation which
> goes to the void on supported branches, especially if there is an
> adequate replacement. Tom, do you think that this is worth updating?
I didn't quite have the energy to do something about it yesterday,
but if you do, feel free.
(I'd suggest looking up the commit that fixed it, to see if it fixed
anything else.)
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Broken link in JSON Types documentation
@ 2019-01-05 03:51 Michael Paquier <michael@paquier.xyz>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 5+ messages in thread
From: Michael Paquier @ 2019-01-05 03:51 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: elisabeth314@gmail.com; pgsql-docs@lists.postgresql.org
On Fri, Jan 04, 2019 at 09:50:34AM -0500, Tom Lane wrote:
> I didn't quite have the energy to do something about it yesterday,
> but if you do, feel free.
>
> (I'd suggest looking up the commit that fixed it, to see if it fixed
> anything else.)
Sure, that was my plan. The change is from d542859, which did not go
to 9.6 and older, and committed. There was one conflict for libpq
which was simple enough to fix, and I have also double-checked the
rest of the docs for rogue links to RFCs.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2019-01-05 03:51 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-01-02 20:01 Broken link in JSON Types documentation PG Doc comments form <noreply@postgresql.org>
2019-01-02 23:11 ` Tom Lane <tgl@sss.pgh.pa.us>
2019-01-04 13:03 ` Michael Paquier <michael@paquier.xyz>
2019-01-04 14:50 ` Tom Lane <tgl@sss.pgh.pa.us>
2019-01-05 03:51 ` Michael Paquier <michael@paquier.xyz>
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