Re: [HACKERS] Getting rid of "unknown error" in dblink andpostgres_fdw - Mailing list pgsql-hackers

From Joe Conway
Subject Re: [HACKERS] Getting rid of "unknown error" in dblink andpostgres_fdw
Date
Msg-id 0267ff84-97a4-41d6-9405-03301c44074b@joeconway.com
Whole thread Raw
In response to Re: [HACKERS] Getting rid of "unknown error" in dblink and postgres_fdw  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12/21/2016 09:27 AM, Tom Lane wrote:
> Joe Conway <mail@joeconway.com> writes:
>> On 12/21/2016 08:49 AM, Tom Lane wrote:
>>> I propose that we should change that string to "could not obtain message
>>> string for error on connection "foo"", or something along that line.
>>>
>>> postgres_fdw has the same disease.  It wouldn't have the notion of a named
>>> connection, but maybe we could insert the foreign server name instead.
>
>> Seems reasonable to me. I can work on it if you'd like. Do you think
>> this should be backpatched?
>
> If you have time for it, please do, I have lots on my plate already.

Ok, will do.

> I'd vote for back-patching; the benefits of a clearer error message
> are obvious, and it hardly seems likely that any existing applications
> are depending on this specific error string.

Agreed.

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] [ patch ] pg_dump: new --custom-fetch-table and--custom-fetch-value parameters
Next
From: David Fetter
Date:
Subject: Re: [HACKERS] pg_background contrib module proposal