Re: Typo in pgbench messages. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Typo in pgbench messages.
Date
Msg-id YhdvuTfHfne5FjCk@paquier.xyz
Whole thread Raw
In response to Re: Typo in pgbench messages.  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: Typo in pgbench messages.  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On Thu, Feb 24, 2022 at 06:38:57PM +0900, Tatsuo Ishii wrote:
> >> I think you are right. In English there's should be no space between number and "%".
> >> AFAIK other parts of PostgreSQL follow the rule.
>
> I think it's better to back-patch this to stable branches if there's
> no objection. Thought?

That's only cosmetic, so I would just bother about HEAD if I were to
change something like that (I would not bother at all, personally).

One argument against a backpatch is that this would be disruptive with
tools that parse and analyze the output generated by pgbench.  Fabien,
don't you have some tools and/or wrappers doing exactly that?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Next
From: Michael Paquier
Date:
Subject: Re: Uniforms the errors msgs at tuplestore paths