Re: Getting rid of "unknown error" in dblink and postgres_fdw
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-12-21T16:55:23Z
Lists: pgsql-hackers
On Wed, Dec 21, 2016 at 9:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > A possible objection is that if we really are on the hairy edge of OOM, > trying to construct such error strings might push us over the edge What am I missing here? Constructing said string occurs on the local end of the connection but the memory problem exists on the remote end. David J.
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