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 1fml2H-0004jd-Hf for pgsql-docs@arkaria.postgresql.org; Mon, 06 Aug 2018 19:19:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fml2E-00044K-SI for pgsql-docs@arkaria.postgresql.org; Mon, 06 Aug 2018 19:19:18 +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 1fml2E-00044D-MW for pgsql-docs@lists.postgresql.org; Mon, 06 Aug 2018 19:19:18 +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 1fml2B-0002BJ-LJ; Mon, 06 Aug 2018 19:19:18 +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 w76JJDNX000661; Mon, 6 Aug 2018 15:19:13 -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: 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> Comments: In-reply-to "Jonathan S. Katz" message dated "Mon, 06 Aug 2018 15:04:30 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <659.1533583153.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 06 Aug 2018 15:19:13 -0400 Message-ID: <660.1533583153@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 2:05 PM, Jonathan S. Katz wrot= e: >> 1. Add to the =E2=80=9Cdocload=E2=80=9D script to segment out the relea= se notes and store >> them in a separate table. Perform an =E2=80=9Cupsert=E2=80=9D (i.e. che= ck for an existing >> reference; if it=E2=80=99s there, update any content, otherwise insert)= . >> = >> 2. Perform any modifications to the content (i.e. there=E2=80=99s some = HTML I >> explicitly removed from the generated docs). >> = >> 3. Display the archived docs on the page. >> = >> That way in future docloads, if there are missing release notes, the sc= ript >> would be ok as it would not remove any release notes. > To proceed, I would want to ensure we feel good about this direction. I = will > also need to discuss with Magnus about how we would want to store this > in pgweb itself. And of course, test it across all the different release= notes > to ensure it works. 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. It's certainly attractive that this doesn't seem like it'd entail any manual effort once it's set up initially. regards, tom lane