pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #17784: broken URL in 15.2 release notes
6+ messages / 3 participants
[nested] [flat]

* BUG #17784: broken URL in 15.2 release notes
@ 2023-02-09 14:20  PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 1 reply; 6+ messages in thread

From: PG Bug reporting form @ 2023-02-09 14:20 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: lizenko79@gmail.com

The following bug has been logged on the website:

Bug reference:      17784
Logged by:          Andrey Lizenko
Email address:      lizenko79@gmail.com
PostgreSQL version: 15.2
Operating system:   all
Description:        

https://www.postgresql.org/docs/release/15.2/
returns

Not Found
The URL you specified does not exist.



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: BUG #17784: broken URL in 15.2 release notes
@ 2023-02-09 14:22  Andrey Lizenko <lizenko79@gmail.com>
  parent: PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 1 reply; 6+ messages in thread

From: Andrey Lizenko @ 2023-02-09 14:22 UTC (permalink / raw)
  To: lizenko79@gmail.com; pgsql-bugs@lists.postgresql.org

Just in case, may be it is a CDN issue.

[image: image.png]

On Thu, 9 Feb 2023 at 15:21, PG Bug reporting form <noreply@postgresql.org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference:      17784
> Logged by:          Andrey Lizenko
> Email address:      lizenko79@gmail.com
> PostgreSQL version: 15.2
> Operating system:   all
> Description:
>
> https://www.postgresql.org/docs/release/15.2/
> returns
>
> Not Found
> The URL you specified does not exist.
>
>

-- 
Regards, Andrei Lizenko

Attachments:

image.png (image/png, 55.6K) download view image
^ permalink raw reply [nested|flat] 6+ messages in thread

* Re: BUG #17784: broken URL in 15.2 release notes
@ 2023-02-09 15:14  Jonathan S. Katz <jkatz@postgresql.org>
  parent: Andrey Lizenko <lizenko79@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Jonathan S. Katz @ 2023-02-09 15:14 UTC (permalink / raw)
  To: Andrey Lizenko <lizenko79@gmail.com>; pgsql-bugs@lists.postgresql.org

On 2/9/23 9:22 AM, Andrey Lizenko wrote:
> Just in case, may be it is a CDN issue.

Just went to the URL. Works for me, and I did not touch any backend 
settings. I don't know if you were at the page prior to the cache flush.

Jonathan



Attachments:

  OpenPGP_signature (application/pgp-signature, 839B) download

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: BUG #17784: broken URL in 15.2 release notes
@ 2023-02-09 15:33  Andrey Lizenko <lizenko79@gmail.com>
  parent: Jonathan S. Katz <jkatz@postgresql.org>
  0 siblings, 1 reply; 6+ messages in thread

From: Andrey Lizenko @ 2023-02-09 15:33 UTC (permalink / raw)
  To: Jonathan S. Katz <jkatz@postgresql.org>; +Cc: pgsql-bugs@lists.postgresql.org

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.

On Thu, 9 Feb 2023 at 16:14, Jonathan S. Katz <jkatz@postgresql.org> wrote:

> On 2/9/23 9:22 AM, Andrey Lizenko wrote:
> > Just in case, may be it is a CDN issue.
>
> Just went to the URL. Works for me, and I did not touch any backend
> settings. I don't know if you were at the page prior to the cache flush.
>
> Jonathan
>
>

-- 
Regards, Andrei Lizenko

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: BUG #17784: broken URL in 15.2 release notes
@ 2023-02-09 16:46  Jonathan S. Katz <jkatz@postgresql.org>
  parent: Andrey Lizenko <lizenko79@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Jonathan S. Katz @ 2023-02-09 16:46 UTC (permalink / raw)
  To: Andrey Lizenko <lizenko79@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org

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



Attachments:

  OpenPGP_signature (application/pgp-signature, 839B) download

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: BUG #17784: broken URL in 15.2 release notes
@ 2023-02-09 18:50  Jonathan S. Katz <jkatz@postgresql.org>
  parent: Jonathan S. Katz <jkatz@postgresql.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Jonathan S. Katz @ 2023-02-09 18:50 UTC (permalink / raw)
  To: Andrey Lizenko <lizenko79@gmail.com>; +Cc: pgsql-bugs@lists.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=ac618d1bb5f8b28ca8766e5ce6e25642f8a36539



Attachments:

  OpenPGP_signature (application/pgp-signature, 839B) download

^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2023-02-09 18:50 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-02-09 14:20 BUG #17784: broken URL in 15.2 release notes PG Bug reporting form <noreply@postgresql.org>
2023-02-09 14:22 ` Andrey Lizenko <lizenko79@gmail.com>
2023-02-09 15:14   ` Jonathan S. Katz <jkatz@postgresql.org>
2023-02-09 15:33     ` Andrey Lizenko <lizenko79@gmail.com>
2023-02-09 16:46       ` Jonathan S. Katz <jkatz@postgresql.org>
2023-02-09 18:50         ` Jonathan S. Katz <jkatz@postgresql.org>

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