Re: redundant error messages

Поиск
Список
Период
Сортировка
От Isaac Morland
Тема Re: redundant error messages
Дата
Msg-id CAMsGm5dnrs69WMq3GK8f5BEWifVh1VVs3kpY2mMCv9PeuBu==g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: redundant error messages  (Euler Taveira <euler.taveira@2ndquadrant.com>)
Ответы Re: redundant error messages
Список pgsql-hackers
Дерево обсуждения
On Thu, 5 Nov 2020 at 08:34, Euler Taveira <euler.taveira@2ndquadrant.com> wrote:

Is the database name important for this message? You should inform which
database you want to connect for all client tools except pg_dumpall. Hence, you
already know which database has the connection problem. IMO the pg_dumpall
message should inform the database name. My suggestion is:

In principle, the client knows the database name. In practice, if it's coming from PGDATABASE or via a service configuration, one may be confused about the database; having the error message be explicit will avoid many problems. I can easily imagine that "unable to connect to database" would be mystifying, whereas "unable to connect to database foo" would elicit the response, "wait, I'm trying to connect to what now?" leading much more quickly to a resolution.

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

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: Re: pg_ls_tmpdir to show directories and shared filesets (and pg_ls_*)
Следующее
От: Seino Yuki
Дата:
Сообщение: Re: enable pg_stat_statements to track rows processed by REFRESH MATERIALIZED VIEW