mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Change the default setting for log_min_error_statement to ERROR. Per

Browse Source 
recent discussion in which majority opinion was that this is a more
widely useful setting than the previous default of PANIC.
This commit is contained in:
Tom Lane 2006-11-21 01:23:37 +00:00
parent e82d9e6283
commit 414c7a537e
3 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/src/sgml/config.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.95 2006/11/12 05:12:42 neilc Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.96 2006/11/21 01:23:37 tgl Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
@ -2474,20 +2474,19 @@ SELECT * FROM parent WHERE key = 2400;
<listitem>
<para>
Controls whether or not the SQL statement that causes an error
condition will also be recorded in the server log. All SQL
statements that cause an error of the specified level or
higher are logged. The default is
<literal>PANIC</literal> (effectively turning this feature
off for normal use). Valid values are <literal>DEBUG5</literal>,
condition will be recorded in the server log. The current
SQL statement is included in the log entry for any message of
the specified severity or higher.
Valid values are <literal>DEBUG5</literal>,
<literal>DEBUG4</literal>, <literal>DEBUG3</literal>,
<literal>DEBUG2</literal>, <literal>DEBUG1</literal>,
<literal>INFO</literal>, <literal>NOTICE</literal>,
<literal>WARNING</literal>, <literal>ERROR</literal>,
<literal>FATAL</literal>, and <literal>PANIC</literal>. For
example, if you set this to <literal>ERROR</literal> then all
SQL statements causing errors, fatal errors, or panics will be
logged. Enabling this parameter can be helpful in tracking down
the source of any errors that appear in the server log.
<literal>FATAL</literal>, and <literal>PANIC</literal>.
The default is <literal>ERROR</literal>, which means statements
causing errors, fatal errors, or panics will be logged.
To effectively turn off logging of failing statements,
set this parameter to <literal>PANIC</literal>.
Only superusers can change this setting.
</para>
</listitem>
@ -2898,7 +2897,7 @@ SELECT * FROM parent WHERE key = 2400;
query protocol, this setting likewise does not log statements that
fail before the Execute phase (i.e., during parse analysis or
planning). Set <varname>log_min_error_statement</> to
<literal>error</> to log such statements.
<literal>ERROR</> (or lower) to log such statements.
</para>
</note>
</listitem>

6
src/backend/utils/misc/guc.c
View File

@ -10,7 +10,7 @@
* Written by Peter Eisentraut <peter_e@gmx.net>.
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/utils/misc/guc.c,v 1.358 2006/11/05 22:42:09 tgl Exp $
* $PostgreSQL: pgsql/src/backend/utils/misc/guc.c,v 1.359 2006/11/21 01:23:37 tgl Exp $
*
*--------------------------------------------------------------------
*/
@ -176,7 +176,7 @@ bool SQL_inheritance = true;
bool Password_encryption = true;
int log_min_error_statement = PANIC;
int log_min_error_statement = ERROR;
int log_min_messages = NOTICE;
int client_min_messages = NOTICE;
int log_min_duration_statement = -1;
@ -1853,7 +1853,7 @@ static struct config_string ConfigureNamesString[] =
"specified level or a higher level are logged.")
},
&log_min_error_statement_str,
"panic", assign_min_error_statement, NULL
"error", assign_min_error_statement, NULL
},
{

5
src/backend/utils/misc/postgresql.conf.sample
View File

@ -284,7 +284,7 @@
#log_error_verbosity = default # terse, default, or verbose messages
#log_min_error_statement = panic # Values in order of increasing severity:
#log_min_error_statement = error # Values in order of increasing severity:
# debug5
# debug4
# debug3
@ -294,7 +294,8 @@
# notice
# warning
# error
# panic(off)
# fatal
# panic (effectively off)
#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
# and their durations.