Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ju0rw-000653-Vr for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Jul 2020 21:47:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ju0rv-0003k1-Sf for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Jul 2020 21:47:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ju0rv-0003jG-Lg for pgsql-hackers@lists.postgresql.org; Fri, 10 Jul 2020 21:47:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ju0rt-0007WJ-3W for pgsql-hackers@lists.postgresql.org; Fri, 10 Jul 2020 21:47:43 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 06ALlc5u2164964; Fri, 10 Jul 2020 17:47:38 -0400 From: Tom Lane To: Thomas Munro cc: Daniel Gustafsson , Magnus Hagander , Kyotaro Horiguchi , PostgreSQL Developers , Bruce Momjian Subject: Re: Stale external URL in doc? In-reply-to: References: <20200709.161226.204639179120026914.horikyota.ntt@gmail.com> <01C59535-7297-4E57-9A7C-D6E2D0E4851A@yesql.se> <1808659.1594302711@sss.pgh.pa.us> Comments: In-reply-to Thomas Munro message dated "Sat, 11 Jul 2020 09:42:17 +1200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2164962.1594417658.1@sss.pgh.pa.us> Date: Fri, 10 Jul 2020 17:47:38 -0400 Message-ID: <2164963.1594417658@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Thomas Munro writes: > The Microsoft one is OK, it's a redirect, but the redirect target > looks like a more permanent URL to me so maybe we should change it. +1 > The others required minor manual sleuthing to correct; I hope I found > the correct ISN ranges page. Please see attached. I didn't actually check any of these, but they look like sane changes. regards, tom lane