Re: reduce size of logs stored by buildfarm

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: reduce size of logs stored by buildfarm
Date: 2025-11-25 17:15:20
Message-ID: a9db7d10-a941-46bc-80b7-d9c616097af3@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2025-11-25 Tu 10:37 AM, Tom Lane wrote:
> =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
>> With these three patches, we go from having 62 MB bytes in files with
>> "log" in their names under testrun/ (except those that have "catalog")
>> to 30 MB. I think that's not a bad reduction.
> I wonder how much this overlaps with what Andrew just did
> to the BF client [1].
>
>
> [1] https://www.postgresql.org/message-id/601bb91d-b55d-4fa6-bb57-c2126fb22620%40dunslane.net
>
>

Pretty much none of it, although both Alvaro and I are clearly motivated
by the same thing, namely disk space pressure on the buildfarm server.

I think his patches 1 and 3 seem like no-brainers.

I did two things in the BF client:

. prevent uploading redundant copies of the same file in meson builds
(this was a bug)

. inhibit loading postmaster log files from installcheck runs and
cross-version upgrade runs, but only if there hasn't been a failure.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-11-25 17:16:39 Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication
Previous Message Andres Freund 2025-11-25 16:54:00 Re: Buffer locking is special (hints, checksums, AIO writes)