From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Addition of %b/backend_type in log_line_prefix of TAP test logs |
Date: | 2025-05-20 23:51:04 |
Message-ID: | aC0VaIWAXLgXcHVP@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
While navigating through the logs in the CI, the buildfarm, or even my
own machine, I've found myself spending a lot of time looking at
very specific log entries to find out the PID of a specific process,
sometimes mistaking a normal backend vs a logical WAL sender while
looking for a PID, or just looking for an auxiliary process.
I'd like to suggest the following change in Cluster.pm:
- print $conf "log_line_prefix = '%m [%p] %q%a '\n";
+ print $conf "log_line_prefix = '%m [%b,%p] %q%a '\n";
It is then possible to match a backend_type with a PID. That
increases the quantity of the logs, of course, but I'm finding that
really helpful to have. But perhaps it's only me?
Thanks,
--
Michael
Attachment | Content-Type | Size |
---|---|---|
tap-logs-backend_type.patch | text/x-diff | 651 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-05-21 00:21:42 | Re: Re: proposal: schema variables |
Previous Message | Masahiko Sawada | 2025-05-20 22:59:04 | Re: Assert("vacrel->eager_scan_remaining_successes > 0") |