Re: Addition of %b/backend_type in log_line_prefix of TAP test logs
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>, Fujii Masao <masao.fujii@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2025-06-20T07:20:21Z
Lists: pgsql-hackers
Attachments
- tap-logs-backend_type-v2.patch (text/x-diff) patch v2
On Sat, May 24, 2025 at 09:09:36AM +0900, Michael Paquier wrote: > On Fri, May 23, 2025 at 11:56:59PM +0900, Fujii Masao wrote: >> On 2025/05/22 8:58, Tom Lane wrote: >>> I'd vote for standardizing on pg_regress.c's spelling, as that's got >>> the most usage history behind it. I'm unexcited about bloating the >>> logs with [%v:%x] --- that's data I've very seldom needed. >> >> +1 Coming back to this thread as v19 is going to open up rather soon, the suggestion from Tom seems to be the consensus reached, which is to use the same value of log_line_prefix in the CI and the TAP as in pg_regress.c. Attached is a patch to do so, that I'd like to apply on HEAD once v19 opens up. If anybody would prefer a backpatch or if anybody has any comments, please feel free. -- Michael
Commits
-
Align log_line_prefix in CI and TAP tests with pg_regress.c
- 5ba00e175a4e 19 (unreleased) landed