From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Release note trimming: another modest proposal
In-reply-to: <660.1533583153@sss.pgh.pa.us>
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>
 <D760BC11-6F2D-4E5D-A6FB-ADC4CA5C9B84@postgresql.org>
 <AE34F1D9-32E5-4B07-B17D-44CF0FB1E30C@postgresql.org>
 <C0D736B2-83FE-4D25-9304-6FA52B749AAB@postgresql.org>
 <660.1533583153@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 06 Aug 2018 15:19:13 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1082.1533583655.1@sss.pgh.pa.us>
Date: Mon, 06 Aug 2018 15:27:35 -0400
Message-ID: <1083.1533583655@sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Hm, so the only objection I can think of is that this results in the old
> release notes only being available on the website; there's no other way
> to access them, short of digging around in the git repo.  But maybe that's
> enough.

Actually, a concrete reason why that might not be good is that it results
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?

This doesn't seem insoluble, but it might mean a bit more work to do
to ensure we can revert back to an earlier version of that table.

			regards, tom lane