Re: [HACKERS] Getting rid of "unknown error" in dblink and postgres_fdw

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] Getting rid of "unknown error" in dblink and postgres_fdw
Дата
Msg-id 1312.1482343733@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] Getting rid of "unknown error" in dblink and postgres_fdw  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] Getting rid of "unknown error" in dblink andpostgres_fdw  (Joe Conway <mail@joeconway.com>)
Список pgsql-hackers
I 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.

BTW, looking closer, I notice that the dblink case already has
         errcontext("Error occurred on dblink connection named \"%s\": %s.",                    dblink_context_conname,
dblink_context_msg)));

so we probably don't need the connection name in the primary error
message.  Now I think "could not obtain message string for remote error"
would be a sufficient message.

In the postgres_fdw case, I'd be inclined to use the same replacement
primary message.  Maybe we should think about adding the server name
to the errcontext there, but that seems like an independent improvement.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Borodin
Дата:
Сообщение: Re: [HACKERS] pg_background contrib module proposal
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)