Re: Typo in pgbench messages.
От | Yugo NAGATA |
---|---|
Тема | Re: Typo in pgbench messages. |
Дата | |
Msg-id | 20220225153924.a29bf2febbd0f7b5720f48f2@sraoss.co.jp обсуждение исходный текст |
Ответ на | Re: Typo in pgbench messages. (Daniel Gustafsson <daniel@yesql.se>) |
Список | pgsql-hackers |
On Thu, 24 Feb 2022 14:44:05 +0100 Daniel Gustafsson <daniel@yesql.se> wrote: > > On 24 Feb 2022, at 13:58, Fabien COELHO <coelho@cri.ensmp.fr> wrote: > > >> 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 throughpipes or scripts. I'd prefer that the format is not changed. Maybe a comment could be added to explain the reasonbehind it. > > That doesn't sound like an overwhelmingly convincing argument to print some > messages with 'X %' and others with 'X%'. I agree with Daniel. If inserting a space in front of % was intentional for handling the result in such tools, we should fix other places where 'X%' is used in the pgbench output. Regards, Yugo Nagata -- Yugo NAGATA <nagata@sraoss.co.jp>
В списке pgsql-hackers по дате отправления: