diff options
| author | Joe Conway | 2016-12-21 23:48:50 +0000 |
|---|---|---|
| committer | Joe Conway | 2016-12-21 23:51:40 +0000 |
| commit | fb0ab06dc4f4c90b85c220418445f4c8f15a59ca (patch) | |
| tree | 583316c86dc036a964d2f4c4435f4b4ababbdf03 | |
| parent | 6e2c21ec5d1c2950c275818a4de6f98ac37da5de (diff) | |
Improve dblink error message when remote does not provide it
When dblink or postgres_fdw detects an error on the remote side of the
connection, it will try to construct a local error message as best it
can using libpq's PQresultErrorField(). When no primary message is
available, it was bailing out with an unhelpful "unknown error". Make
that message better and more style guide compliant. Per discussion
on hackers.
Backpatch to 9.2 except postgres_fdw which didn't exist before 9.3.
Discussion: https://postgr.es/m/19872.1482338965%40sss.pgh.pa.us
| -rw-r--r-- | contrib/dblink/dblink.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/dblink/dblink.c b/contrib/dblink/dblink.c index 6f972be0d7f..e6eb7075d0b 100644 --- a/contrib/dblink/dblink.c +++ b/contrib/dblink/dblink.c @@ -2633,7 +2633,7 @@ dblink_res_error(const char *conname, PGresult *res, const char *dblink_context_ ereport(level, (errcode(sqlstate), message_primary ? errmsg_internal("%s", message_primary) : - errmsg("unknown error"), + errmsg("could not obtain message string for remote error"), message_detail ? errdetail_internal("%s", message_detail) : 0, message_hint ? errhint("%s", message_hint) : 0, message_context ? errcontext("%s", message_context) : 0, |