Re: Getting rid of "unknown error" in dblink and postgres_fdw
Joe Conway <mail@joeconway.com>
From: Joe Conway <mail@joeconway.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2016-12-22T17:54:32Z
Lists: pgsql-hackers
On 12/22/2016 06:55 AM, Tom Lane wrote: > Joe Conway <mail@joeconway.com> writes: >> On 12/21/2016 09:20 PM, Tom Lane wrote: >>> I see that you need to pass the PGconn into dblink_res_error() now, but >>> what's the point of the new "bool fail" parameter? > >> That part isn't new -- we added it sometime prior to 9.2: > > Oh! I misread the patch --- something about an unluckily-placed line > wrap and not looking very closely :-(. Yeah, it's fine as is. > Sorry for the noise. Thanks -- committed/backpatched to 9.2 Joe -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
Commits
-
Make dblink try harder to form useful error messages
- 2f802d95b490 10.0 landed
- 51126ccdb1ce 9.6.2 landed
- 80ca22aa60a6 9.5.6 landed
- 76943f54a743 9.4.11 landed
- 9b8507bfae91 9.3.16 landed
- 44de099f89c2 9.2.20 landed
-
Improve dblink error message when remote does not provide it
- 88673c9d3bc7 9.6.2 landed
- 28c9b6be7f76 9.5.6 landed
- 0f5b1867c2e6 9.4.11 landed
- 3272be346895 9.3.16 landed
- fb0ab06dc4f4 9.2.20 landed
- ea0aa9698cfa 10.0 landed