Re: reduce size of logs stored by buildfarm - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: reduce size of logs stored by buildfarm
Date
Msg-id a9db7d10-a941-46bc-80b7-d9c616097af3@dunslane.net
Whole thread Raw
In response to Re: reduce size of logs stored by buildfarm  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: reduce size of logs stored by buildfarm
List pgsql-hackers
On 2025-11-25 Tu 10:37 AM, Tom Lane wrote:
> =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.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




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Buffer locking is special (hints, checksums, AIO writes)
Next
From: Fujii Masao
Date:
Subject: Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication