Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fmlKC-0005kk-HW for pgsql-docs@arkaria.postgresql.org; Mon, 06 Aug 2018 19:37:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fmlKA-00036Y-Js for pgsql-docs@arkaria.postgresql.org; Mon, 06 Aug 2018 19:37:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fmlKA-00036Q-E0 for pgsql-docs@lists.postgresql.org; Mon, 06 Aug 2018 19:37:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fmlK7-0002hd-Fd; Mon, 06 Aug 2018 19:37:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w76Jbja5001621; Mon, 6 Aug 2018 15:37:45 -0400 From: Tom Lane To: "Jonathan S. Katz" cc: pgsql-docs@lists.postgresql.org Subject: Re: Release note trimming: another modest proposal In-reply-to: <1F8EA64B-695C-4893-A436-B655C840788D@postgresql.org> References: <19252.1533509841@sss.pgh.pa.us> <37D00E58-A0F0-42E4-83F1-A124A282575D@postgresql.org> <18020.1533568149@sss.pgh.pa.us> <04F6EF85-C7B7-42F3-84BC-D5670C9D77E1@postgresql.org> <19825.1533570442@sss.pgh.pa.us> <3070E803-B5D5-46DA-80E5-47B43BE9B085@postgresql.org> <23297.1533574521@sss.pgh.pa.us> <660.1533583153@sss.pgh.pa.us> <1083.1533583655@sss.pgh.pa.us> <1F8EA64B-695C-4893-A436-B655C840788D@postgresql.org> Comments: In-reply-to "Jonathan S. Katz" message dated "Mon, 06 Aug 2018 15:30:18 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1619.1533584264.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 06 Aug 2018 15:37:45 -0400 Message-ID: <1620.1533584265@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Jonathan S. Katz" writes: >> On Aug 6, 2018, at 3:27 PM, Tom Lane wrote: >> Actually, a concrete reason why that might not be good is that it resul= ts >> in having a single point of failure: once we remove branch N's relnotes >> from the active branches, the only copy of that data is the one in the >> archive table the docload script is filling. Given, say, a bug in the >> docload script that causes it to overwrite the wrong table entries, >> can we recover? > Well, the release notes are still in the git history as well as the tarb= alls. > One could always pull an older tarball of PostgreSQL with the full > release.sgml and load from there. True ... as long as those older tarballs represent data that our current workflow can process. For instance, if we did another documentation format change (from XML to something else), the older tarballs would perhaps no longer be useful for this purpose. On the other hand, it's hard to believe that we'd make such a conversion without tools to help. So probably if the situation came up, we could cobble together something that would allow ingesting the old format. regards, tom lane