Re: Having postgresql.org link to cgit instead of gitweb

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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:38:55
Message-ID: 5b87b69e-fd9a-45e9-b139-fe2cf88d05e9@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/22/25 11:27 AM, Álvaro Herrera wrote:
> 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.

I'm fine with this approach, for the above reasons. The web patch won't
bit shift too much between now and then.

Jonathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-09-22 15:41:17 Re: waiteventset.c XXX
Previous Message Álvaro Herrera 2025-09-22 15:27:46 Re: Having postgresql.org link to cgit instead of gitweb