Joe Conway 3272be3468 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		2016-12-21 15:51:46 -08:00
..
expected	Lock down regression testing temporary clusters on Windows.	2014-12-17 22:48:46 -05:00
input	Diagnose incompatible OpenLDAP versions during build and test.	2014-07-22 11:01:41 -04:00
output	Diagnose incompatible OpenLDAP versions during build and test.	2014-07-22 11:01:41 -04:00
sql	Lock down regression testing temporary clusters on Windows.	2014-12-17 22:48:46 -05:00
.gitignore
dblink--1.0--1.1.sql	Backpatch: Fix typo in update scripts for some contrib modules.	2014-08-25 18:30:46 +02:00
dblink--1.1.sql
dblink--unpackaged--1.0.sql	Fix typos in some error messages thrown by extension scripts when fed to psql.	2014-08-25 18:30:46 +02:00
dblink.c	Improve dblink error message when remote does not provide it	2016-12-21 15:51:46 -08:00
dblink.control
dblink.h
Makefile	Lock down regression testing temporary clusters on Windows.	2014-12-17 22:48:46 -05:00
pg_service.conf	Diagnose incompatible OpenLDAP versions during build and test.	2014-07-22 11:01:41 -04:00