Re: not translating backend types for ps and log_line_prefix - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: not translating backend types for ps and log_line_prefix
Date
Msg-id a23ae86a-af89-4da1-9476-bf7dd6e557f2@iki.fi
Whole thread Raw
In response to not translating backend types for ps and log_line_prefix  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: not translating backend types for ps and log_line_prefix
List pgsql-hackers
On 10/12/2025 15:45, Álvaro Herrera wrote:
> Hello,
> 
> Pursuant to my comments in [1], I attach a patch that restricts the use
> of translated process types as indicated in $SUBJECT.  This adds a
> separate column to the process type list, mostly extracted from Euler's
> patch, not marked for translation, and uses it in a couple of places.
> I think this is more reasonable.  I chose to CC Heikki here because the
> business with translating these strings was, as I recall, his doing ...
> 
> [1] https://postgr.es/m/202512091806.bsugq2l4wz7f@alvherre.pgsql

Hm, I don't think I've changed how they're translated. At least not 
intentionally.

> +PG_PROCTYPE(B_AUTOVAC_LAUNCHER, "autovacuum", gettext_noop("autovacuum launcher"), AutoVacLauncherMain, true)
> +PG_PROCTYPE(B_AUTOVAC_WORKER, "autovacuum", gettext_noop("autovacuum worker"), AutoVacWorkerMain, true)

It seems not nice that both have the same name, "autovacuum". Similarly, 
I think it's good to have different names for dead-end backends and 
regular backends.

No objections to the general idea, although I think the current 
descriptions are fairly short already.

- Heikki




pgsql-hackers by date:

Previous
From: "Greg Burd"
Date:
Subject: Re: [PATCH] Fix ARM64/MSVC atomic memory ordering issues on Win11 by adding explicit DMB ​barriers
Next
From: Nico Williams
Date:
Subject: Re: Solaris versus our NLS files