From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Andrey Lizenko <lizenko79(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17784: broken URL in 15.2 release notes |
Date: | 2023-02-09 16:46:03 |
Message-ID: | 971e5a12-5f98-7b41-6782-f8a090447328@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2023-02-09 18:50:33 | Re: BUG #17784: broken URL in 15.2 release notes |
Previous Message | Tomas Vondra | 2023-02-09 16:18:47 | Re: BUG #17774: Assert triggered on brin_minmax_multi.c |