From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Having postgresql.org link to cgit instead of gitweb |
Date: | 2025-09-22 15:27:46 |
Message-ID: | 202509221524.dalen7wjv4iv@alvherre.pgsql |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-Sep-22, Tom Lane wrote:
> My first thought about scheduling was "best not in the middle of the
> 18.0 release cycle". However, I don't know of any actual connection
> between gitweb/cgit and the release-making tasks. My second thought
> was "the point here is to cut server load, and maybe we need that to
> happen before the anticipated traffic spike on Thursday". There
> might not be any connection there either, but if there is, agreed
> to get it done sooner not later.
I think the traffic overloads are mostly caused by LLM scrapers, which
as far as I know does not correlate with spikes caused by human behavior
or even those caused by mirroring traffic during a new release or such.
I would rather wait until next week, just in case something breaks.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"This is what I like so much about PostgreSQL. Most of the surprises
are of the "oh wow! That's cool" Not the "oh shit!" kind. :)"
Scott Marlowe, http://archives.postgresql.org/pgsql-admin/2008-10/msg00152.php
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2025-09-22 15:38:55 | Re: Having postgresql.org link to cgit instead of gitweb |
Previous Message | Jeff Davis | 2025-09-22 15:26:28 | Re: Use WALReadFromBuffers in more places |