Re: reduce size of logs stored by buildfarm
Jacob Champion <jacob.champion@enterprisedb.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-11-25T18:39:29Z
Lists: pgsql-hackers
Attachments
- truncate-JSON-logs.patch.txt (text/plain)
On Tue, Nov 25, 2025 at 5:30 AM Álvaro Herrera <alvherre@kurilemu.de> wrote: > I also noticed that an oauth test file contains a couple MBs of a > gigantic string of just 'x'. I suppose that will compress well (with > gzip at least, the 2 MB file becomes 8 kB). Still, it's kinda > ridiculous and useless to bloat a 67 kB file to 2 MB that way. Sorry about that. > 0003 does that by simply cutting the string short at 10k, which reduces > the size of the log from 2 MB to some 86 kB. Maybe there are better > ways to deal with this? Jacob? Only thing I don't like about this is that the JSON you need for debugging might be after the useless padding. Attached is a patch that does things more surgically, tested against Python 3.6, and I'm running it through the CI now. Thanks, --Jacob
Commits
-
oauth_validator: Shorten JSON responses in test logs
- 3d8183e7c473 18.2 landed
- 47c7a7ebc89e 19 (unreleased) landed
-
pg_dump tests: don't put dumps in stdout
- 33bb3dc2d855 19 (unreleased) landed
- 0e4b1af78d7c 18.2 landed