Re: strange error reporting - Mailing list pgsql-hackers

From Robert Haas
Subject Re: strange error reporting
Date
Msg-id CA+TgmoZQO6Bj-ezpnjp7UZ6UzLTJVNa1nW5=aOGLb0WD990L2Q@mail.gmail.com
Whole thread Raw
In response to Re: strange error reporting  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: strange error reporting  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Wed, Jan 20, 2021 at 1:25 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> That's because pgbench reports the input argument dbname, but since you
> didn't specify anything, then PQconnectdbParams() uses the libpq
> behavior.  I think we'd have to use PQdb() instead.

I figured it was something like that. I don't know whether the right
thing is to use something like PQdb() to get the correct database
name, or whether we should go with Tom's suggestion and omit that
detail altogether, but I think showing the empty string when the user
relied on the default is too confusing.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: strange error reporting
Next
From: Alvaro Herrera
Date:
Subject: Re: strange error reporting