Re: VACUUM (PARALLEL) option processing not using DefElem the way it was intended - Mailing list pgsql-hackers

From David Rowley
Subject Re: VACUUM (PARALLEL) option processing not using DefElem the way it was intended
Date
Msg-id CAApHDvruL7RTwpuPg4NdJZ8E1dVbSAVXYgBPn02kC_os6oHHJQ@mail.gmail.com
Whole thread Raw
In response to Re: VACUUM (PARALLEL) option processing not using DefElem the way it was intended  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: VACUUM (PARALLEL) option processing not using DefElem the way it was intended
List pgsql-hackers
On Thu, 9 Oct 2025 at 00:36, Álvaro Herrera <alvherre@kurilemu.de> wrote:
> Yeah, that change makes sense to me.  With an eye towards not forcing
> the translators to understand the message context or forced to translate
> the word "parallel", I would suggest to take the option name out of the
> sentence, maybe something like
>
>   value for VACUUM option \"%s\" must be between 0 and %d

Just looking at the other error messages. They all seems to put the
option in upper case but not in quotes. Following along with those,
we'd end up with:

PARALLEL option must be between 0 and %d

Would that be enough to help the translator understand not to
translate the option name?

David



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: duplicate logging in pg_createsubscriber
Next
From: shveta malik
Date:
Subject: Re: Logical Replication of sequences