From: Jonathan S. Katz <jkatz@postgresql.org>
To: Andrey Lizenko <lizenko79@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17784: broken URL in 15.2 release notes
Date: Thu, 9 Feb 2023 13:50:33 -0500
Message-ID: <e913c749-04dc-455a-5c20-0c9c12f8e470@postgresql.org> (raw)
In-Reply-To: <971e5a12-5f98-7b41-6782-f8a090447328@postgresql.org>
References: <17784-4b66b9608fb6f896@postgresql.org>
<CADKuZZAJ8_V5wX-wiMGz1FJVzFY6dyCQUs8okKfvKBTOLChufw@mail.gmail.com>
<974efd6a-ad64-7583-5d8d-b44eae1edb8d@postgresql.org>
<CADKuZZAn6vc_2rLDnjoA-XXwdOv72baZfEhG89UoN-VbB_17yg@mail.gmail.com>
<971e5a12-5f98-7b41-6782-f8a090447328@postgresql.org>
On 2/9/23 11:46 AM, Jonathan S. Katz wrote:
> On 2/9/23 10:33 AM, Andrey Lizenko wrote:
>> No, its ok for now, but didn't work for a quite short time, that is
>> why, I've checked it in a fresh cacheless FF, instead of usual Chrome.
>> My suggestion about CDN were also about it - we just need to wait.
>
> Well, on the pgweb side (the website code) we should ensure that the
> release notes are available. As part of the release SOP we do have a
> step to clear the release notes cache prior to launch. I clearly did not
> do that -- when I did my quick test it appeared to be OK, but that was
> only on the 15.2 notes.
>
> We do have code to automatically purge portions of the cache when
> certain models update, and on inspection we don't do that when we push
> out the releases and update the versions. I'm going to work on a fix for
> that, as this has now happened a few times (and granted, is typically my
> fault) but should be easy enough to automate.
Per a discussion on -www, we pushed a fix that should prevent (or at
least better mitigate) the risk that this happens in the future[1].
Thanks!
Jonathan
[1]
https://git.postgresql.org/gitweb/?p=pgweb.git;a=commit;h=ac618d1bb5f8b28ca8766e5ce6e25642f8a36539Attachments:
OpenPGP_signature (application/pgp-signature, 839B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: jkatz@postgresql.org, lizenko79@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17784: broken URL in 15.2 release notes
In-Reply-To: <e913c749-04dc-455a-5c20-0c9c12f8e470@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox