Re: log_min_messages per backend type - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: log_min_messages per backend type
Date
Msg-id 202512091806.bsugq2l4wz7f@alvherre.pgsql
Whole thread Raw
In response to Re: log_min_messages per backend type  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: log_min_messages per backend type
List pgsql-hackers
On 2025-Dec-09, Alvaro Herrera wrote:

> So here's your v6 again with those fixes as 0003 -- let's see what CI
> thinks of this.  I haven't looked at your doc changes yet.

This passed CI, so I have marked it as Ready for Committer.  Further
comments are still welcome, of course, but if there are none, I intend
to get it committed in a few days.


I'm not really happy with our usage of the translatable description
field for things such as %b in log_line_prefix or the ps display; I
think we should use the shorter names there instead.  Otherwise, you end
up with log lines that look something like this (visible in a server
with %b in log_line_prefix, which the TAP tests as well as pg_regress
have):

  2025-12-08 21:38:04.304 CET autovacuum launcher[2452437] DEBUG: autovacuum launcher started

where the bit before the PID is marked for translation.  I think it
should rather be

  2025-12-08 21:38:04.304 CET autovacuum[2452437] DEBUG: autovacuum launcher started

where that name (the same we'll use in log_min_messages) is not
translated.

However, this issue is rather independent of the patch in this thread,
so I'm going to discuss it in another thread; the name string though is
added by this patch.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"Java is clearly an example of money oriented programming"  (A. Stepanov)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Let's add a test for NLS translation of PRI* macros
Next
From: Matthias van de Meent
Date:
Subject: Re: making tid and HOTness of UPDATE available to logical decoding plugins