Improvement of log messages in pg_basebackup - Mailing list pgsql-hackers

From Fujii Masao
Subject Improvement of log messages in pg_basebackup
Date
Msg-id CAHGQGwEbvxuDSCoT6EG+RiEp7-O6Wp+ozzEYnJmpmfsYpc9yqg@mail.gmail.com
Whole thread Raw
Responses Re: Improvement of log messages in pg_basebackup  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

>    fprintf(stderr, _("%s: could not identify system: %s\n"),
>            progname, PQerrorMessage(conn));

Since PQerrorMessage() result includes a trailing newline, the above
log message in pg_basebackup doesn't need to include a trailing \n.
Attached patch gets rid of that \n.

>    res = PQgetResult(conn);
>    if (PQresultStatus(res) != PGRES_TUPLES_OK)
>    {
>        fprintf(stderr, _("%s: could not get WAL end position from server\n"),
>                progname);

ISTM it's worth including PQerrorMessage() result in the above log
message, to diagnose the cause of error. Attached patch does that.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)
Next
From: "Albe Laurenz"
Date:
Subject: Re: pgsql_fdw, FDW for PostgreSQL server