You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Avoid redundantly prefixing PQerrorMessage for a connection failure.
libpq's error messages for connection failures pretty well stand ontheir own, especially since commits52a1022/27a48e5a1. Prefixingthem with 'could not connect to database "foo"' or the like is justredundant, and perhaps even misleading if the specific database nameisn't relevant to the failure. (When it is, we trust that thebackend's error message will include the DB name.) Indeed, psqlhasn't used any such prefix in a long time. So, make all our otherprograms and documentation examples agree with psql's practice.Discussion:https://postgr.es/m/1094524.1611266589@sss.pgh.pa.us