From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: elisabeth314@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Broken link in JSON Types documentation
In-reply-to: <20190104130303.GE2067@paquier.xyz>
References: <154645929104.5292.17420414597290599745@wrigleys.postgresql.org>
 <12837.1546470715@sss.pgh.pa.us> <20190104130303.GE2067@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Fri, 04 Jan 2019 22:03:03 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9014.1546613434.1@sss.pgh.pa.us>
Date: Fri, 04 Jan 2019 09:50:34 -0500
Message-ID: <9015.1546613434@sss.pgh.pa.us>
Precedence: bulk

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