| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Á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 18:39:29 |
| Message-ID: | CAOYmi+mF9Mkwzd2cn+mW8JKx-fscJO_VPWchCW6shkZvC-OjYQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 25, 2025 at 5:30 AM Álvaro Herrera <alvherre(at)kurilemu(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| truncate-JSON-logs.patch.txt | text/plain | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-11-25 18:46:03 | Re: reduce size of logs stored by buildfarm |
| Previous Message | Álvaro Herrera | 2025-11-25 18:14:56 | Re: reduce size of logs stored by buildfarm |