database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-20 15:22:23 +03:00
Code Activity

Add an errdetail_internal() ereport auxiliary routine.

Browse Source 
This function supports untranslated detail messages, in the same way that
errmsg_internal supports untranslated primary messages.  We've needed this
for some time IMO, but discussion of some cases in the SSI code provided
the impetus to actually add it.

Kevin Grittner, with minor adjustments by me
This commit is contained in:
Tom Lane
2011-07-16 13:41:48 -04:00
parent 0886dde5f8
commit ed7ed76712
3 changed files with 51 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
doc/src/sgml/sources.sgml
View File

@ -214,13 +214,12 @@ ereport(ERROR,
</listitem>
<listitem>
<para>
<function>errdetail_log(const char *msg, ...)</function> is the same as
<function>errdetail</> except that this string goes only to the server
log, never to the client. If both <function>errdetail</> and
<function>errdetail_log</> are used then one string goes to the client
and the other to the log. This is useful for error details that are
too security-sensitive or too bulky to include in the report
sent to the client.
<function>errdetail_internal(const char *msg, ...)</function> is the same
as <function>errdetail</>, except that the message string will not be
translated nor included in the internationalization message dictionary.
This should be used for detail messages that are not worth expending
translation effort on, for instance because they are too technical to be
useful to most users.
</para>
</listitem>
<listitem>
@ -231,6 +230,18 @@ ereport(ERROR,
For more information see <xref linkend="nls-guidelines">.
</para>
</listitem>
<listitem>
<para>
<function>errdetail_log(const char *msg, ...)</function> is the same as
<function>errdetail</> except that this string goes only to the server
log, never to the client. If both <function>errdetail</> (or one of
its equivalents above) and
<function>errdetail_log</> are used then one string goes to the client
and the other to the log. This is useful for error details that are
too security-sensitive or too bulky to include in the report
sent to the client.
</para>
</listitem>
<listitem>
<para>
<function>errhint(const char *msg, ...)</function> supplies an optional