Re: [INTERFACES] Upgrading the backend's error-message infrastructure

Tom Lane writes:

> M Message --- the string is the primary error message (localized).
> D Detail --- secondary error message, carrying more detail about
> the problem (localized).
> H Hint --- a suggestion what to do about the error (localized).

Client interfaces for the most part only have the notion of a single
"message text". (And keep in mind that the definitions of most interfaces
are outside our control: JDBC, ODBC, ECPG, Perl DBI, PHP, etc.) So what
kind of functionality is needed so that standardized interfaces can get at
any of the provided details and hints?

Maybe this doesn't need to be solved at the protocol layer. Instead a
server-side switch regulates the detail of the provided messages.

Also, how do we control what amount of detail is written to the server
log?

--
Peter Eisentraut peter_e(at)gmx(dot)net