Re: Inconsistent style in pgbench's error messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inconsistent style in pgbench's error messages
Date: 2015-07-06 14:07:42
Message-ID: 25977.1436191662@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> Personally I think "pgbench: " adds very little and so I'd rather get
>> rid of it, but I'm sure others feel differently.

> I think that one of the reason for this is that once pgbench started to
> run it is desirable to differentiate error messages that come from libpq
> and those that come from pgbench itsef.

Don't really see the issue. Errors reported by the server are easy to
distinguish by formatting (as long as we don't go out of our way to make
pgbench's errors look like them, which is one reason I do not like the
"HINT" proposal in the bug #12379 thread). Errors reported by libpq
itself might look like they came from pgbench, but I don't exactly see
what's wrong with that. I don't think users much care about the
difference, as long as they can tell server-side errors apart from
client-side errors.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2015-07-06 14:08:25 Re: dblink: add polymorphic functions.
Previous Message Heikki Linnakangas 2015-07-06 14:06:17 Re: PATCH:do not set Win32 server-side socket buffer size on windows 2012