[COMMITTERS] pgsql: Improve dblink error message when remote does not provide it - Mailing list pgsql-committers

From Joe Conway
Subject [COMMITTERS] pgsql: Improve dblink error message when remote does not provide it
Date
Msg-id E1cJqh6-0007Kp-I9@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/fb0ab06dc4f4c90b85c220418445f4c8f15a59ca

Modified Files
--------------
contrib/dblink/dblink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Joe Conway
Date:
Subject: [COMMITTERS] pgsql: Improve dblink error message when remote does not provide it
Next
From: Michael Meskes
Date:
Subject: [COMMITTERS] pgsql: Fix buffer overflow on particularly named files and clarifydocu