database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Avoid redundantly prefixing PQerrorMessage for a connection failure.

Browse Source 
libpq's error messages for connection failures pretty well stand on
their own, especially since commits 52a10224e/27a48e5a1.  Prefixing
them with 'could not connect to database "foo"' or the like is just
redundant, and perhaps even misleading if the specific database name
isn't relevant to the failure.  (When it is, we trust that the
backend's error message will include the DB name.)  Indeed, psql
hasn't used any such prefix in a long time.  So, make all our other
programs and documentation examples agree with psql's practice.

Discussion: https://postgr.es/m/1094524.1611266589@sss.pgh.pa.us
This commit is contained in:
Tom Lane
2021-01-22 16:52:31 -05:00
parent 7cd9765f9b
commit 58cd8dca3d
21 changed files with 31 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
contrib/oid2name/oid2name.c
View File

@ -347,8 +347,7 @@ sql_conn(struct options *my_opts)
/* check to see that the backend connection was successfully made */
if (PQstatus(conn) == CONNECTION_BAD)
{
pg_log_error("could not connect to database %s: %s",
my_opts->dbname, PQerrorMessage(conn));
pg_log_error("%s", PQerrorMessage(conn));
PQfinish(conn);
exit(1);
}