Re: BUG #12379: pgbench should hint to pgbench -i - Mailing list pgsql-bugs

From Fabien COELHO
Subject Re: BUG #12379: pgbench should hint to pgbench -i
Date
Msg-id alpine.DEB.2.10.1505211001110.14769@sto
Whole thread Raw
In response to Re: BUG #12379: pgbench should hint to pgbench -i  (Oleksandr Shulgin <oleksandr.shulgin@zalando.de>)
Responses Re: BUG #12379: pgbench should hint to pgbench -i  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
List pgsql-bugs
Hello Oleksandr,

>> HINT:  is "foo" the right database? did you initialize first (pgbench -i)?
>
> I don't think there is precedent for spitting out "HINT:" in client code
> (at least grep didn't find it).  So this message might look like it's
> coming from the server, while it doesn't.

I do not see that as a problem. From my point of view a "HINT" is just
what it is, and the message says clearly that it comes from pgbench.

> I think the following is closer to pre-existing experience, IMO:
> + fprintf(stderr, "Is \"%s\" the right database? Did you initialize it first (pgbench -i)?\n", dbName);

Hmmm. I liked to have a prefix on the line, that gives a purpose to the
sentence. Maybe:

   HINT (pgbench):  Is "foo" the right database? Did you initialize (-i) first?

Or

   pgbench:  ...

Or

   pgbench HINT:  ...

--
Fabien.

pgsql-bugs by date:

Previous
From: Oleksandr Shulgin
Date:
Subject: Re: BUG #12379: pgbench should hint to pgbench -i
Next
From: "Shulgin, Oleksandr"
Date:
Subject: Re: BUG #12379: pgbench should hint to pgbench -i