Re: VACUUM (PARALLEL) option processing not using DefElem the way it was intended

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: VACUUM (PARALLEL) option processing not using DefElem the way it was intended
Date: 2025-10-08 11:50:45
Message-ID: CAApHDvruL7RTwpuPg4NdJZ8E1dVbSAVXYgBPn02kC_os6oHHJQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 9 Oct 2025 at 00:36, Álvaro Herrera <alvherre(at)kurilemu(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2025-10-08 12:01:40 Re: Logical Replication of sequences
Previous Message Michael Paquier 2025-10-08 11:46:42 Re: duplicate logging in pg_createsubscriber