Re: Addition of %b/backend_type in log_line_prefix of TAP test logs - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Addition of %b/backend_type in log_line_prefix of TAP test logs
Date
Msg-id CAHGQGwHy+QNJw6bYWFa0fLb7smpmARfqv51vJ0BX8DHRaqsd_Q@mail.gmail.com
Whole thread Raw
In response to Addition of %b/backend_type in log_line_prefix of TAP test logs  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Wed, May 21, 2025 at 8:51 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> 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";

+1 to this change.

Since pg_regress uses log_line_prefix = '%m %b[%p] %q%a ',
isn't it better to use the same setting in TAP tests as well?

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Regression in statement locations
Next
From: Fujii Masao
Date:
Subject: Re: [BUG] Skipped initialization of some xl_xact_parsed_prepare fields