diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-01-21 16:10:18 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-01-21 16:10:18 -0500 |
| commit | 27a48e5a16ff2227ddf44ee717d9bcd89d22a7aa (patch) | |
| tree | 7b1861a7d0f35c213a1a8e0db54a13daeb07cd81 /src/backend/access/gist | |
| parent | 55dc86eca70b1dc18a79c141b3567efed910329d (diff) | |
| download | postgresql-27a48e5a16ff2227ddf44ee717d9bcd89d22a7aa.tar.gz postgresql-27a48e5a16ff2227ddf44ee717d9bcd89d22a7aa.zip | |
Improve new wording of libpq's connection failure messages.
"connection to server so-and-so failed:" seems clearer than the
previous wording "could not connect to so-and-so:" (introduced by
52a10224e), because the latter suggests a network-level connection
failure. We're now prefixing this string to all types of connection
failures, for instance authentication failures; so we need wording
that doesn't imply a low-level error.
Per discussion with Robert Haas.
Discussion: https://postgr.es/m/CA+TgmobssJ6rS22dspWnu-oDxXevGmhMD8VcRBjmj-b9UDqRjw@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions