Tom Lane 58cd8dca3d Avoid redundantly prefixing PQerrorMessage for a connection failure. ... 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		2021-01-22 16:52:31 -05:00
..
t
.gitignore
Makefile
oid2name.c	Avoid redundantly prefixing PQerrorMessage for a connection failure.	2021-01-22 16:52:31 -05:00