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

From Fabien COELHO
Subject Re: Typo in pgbench messages.
Date
Msg-id alpine.DEB.2.22.394.2202241349460.2679704@pseudo
Whole thread Raw
In response to Re: Typo in pgbench messages.  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Typo in pgbench messages.  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
Bonjour Michaël,

>> 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?

Yep, I like to "| cut -d' ' -fx" and other "line.split(' ')" or whatever.

I think that the break of typographical rules is intentional to allow such 
simplistic low-level stream handling through pipes or scripts. I'd prefer 
that the format is not changed. Maybe a comment could be added to explain 
the reason behind it.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Buffer Manager and Contention
Next
From: Masahiko Sawada
Date:
Subject: Re: Optionally automatically disable logical replication subscriptions on error