8000 Request verbose error message output in bug reports. · codeimmortal/postgres@0019532 · GitHub
[go: up one dir, main page]

Skip to content

Commit 0019532

Browse files
committed
Request verbose error message output in bug reports.
1 parent 5bfb054 commit 0019532

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

doc/src/sgml/problems.sgml

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/problems.sgml,v 2.14 2003/04/13 09:56:00 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/problems.sgml,v 2.15 2003/08/10 01:19:18 tgl Exp $
33
-->
44

55
<sect1 id="bug-reporting">
@@ -167,6 +167,16 @@ $Header: /cvsroot/pgsql/doc/src/sgml/problems.sgml,v 2.14 2003/04/13 09:56:00 pe
167167
it might not happen on our platform. The easiest thing is to copy the output
168168
from the terminal, if possible.
169169
</para>
170+
<note>
171+
<para>
172+
If you are reporting an error message, please obtain the most verbose
173+
form of the message. In <application>psql</>, say <literal>\set
174+
VERBOSITY verbose</> beforehand. If you are extracting the message
175+
from the server log, set the run-time parameter
176+
<varname>log_error_verbosity</> to <literal>verbose</> so that all
177+
details are logged.
178+
</para>
179+
</note>
170180
<note>
171181
<para>
172182
In case of fatal errors, the error message reported by the client might

0 commit comments

Comments
 (0)
0