Re: redundant error messages - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: redundant error messages
Date
Msg-id CAH503wAbpk-isL-tCiM=FpaVD1Yb9NXtfw-M869KwEvaSRhi8Q@mail.gmail.com
Whole thread Raw
In response to redundant error messages  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: redundant error messages  (Isaac Morland <isaac.morland@gmail.com>)
List pgsql-hackers
On Thu, 5 Nov 2020 at 09:27, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
A few client tools duplicate error messages already provided by libpq,
such as

pg_rewind: fatal: could not connect to server: could not connect to
server: No such file or directory

Good catch!
 
Other client tools provide a different error message so in aggregate it
looks like this:

createdb: error: could not connect to database template1: could not
connect to server: No such file or directory

Is the database name important for this message? You should inform which
database you want to connect for all client tools except pg_dumpall. Hence, you
already know which database has the connection problem. IMO the pg_dumpall
message should inform the database name. My suggestion is:

        if (fail_on_error)
        {  
            pg_log_error("database \"%s\": %s",
                         dbname, PQerrorMessage(conn));
            exit_nicely(1);
        }

and remove the redundant 'could not connect to database %s' from
scripts/common.c.


--
Euler Taveira                 http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: "Hou, Zhijie"
Date:
Subject: RE: Parallel copy
Next
From: Justin Pryzby
Date:
Subject: Re: pg_ls_tmpdir to show directories and shared filesets (and pg_ls_*)