Skip site navigation (1) Skip section navigation (2)

log_statements = mod or all

From: fatih ozturk <ozturkfa(at)yahoo(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: log_statements = mod or all
Date: 2009-04-09 08:15:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin

log_statement explained as

log_statement (string)        Controls which SQL statements are logged. Valid values are         none, ddl, mod, and         all. ddl logs all data definition         statements, such as CREATE, ALTER, and         DROP statements. mod logs all         ddl statements, plus data-modifying statements         such as INSERT,         UPDATE, DELETE, TRUNCATE,         and COPY FROM.         PREPARE, EXECUTE, and         EXPLAIN ANALYZE
statements are also logged if their contained command is of an
appropriate type. For clients using extended query protocol, logging
occurs when an Execute message is received, and values of the Bind
parameters are included (with any embedded single-quote marks doubled).
        The default is none. Only superusers can change this         setting.        Note:          Statements that contain simple syntax errors are not logged          even by the log_statement = all
setting, because the log message is emitted only after basic parsing
has been done to determine the statement type. In the case of extended
query protocol, this setting likewise does not log statements that fail
before the Execute phase (i.e., during parse analysis or planning). Set
log_min_error_statement to          ERROR (or lower) to log such statements.               "
Problem is i dont understand the difference between log_statement='all' and log_statement='mod'?

Am i missing something?

Thanks for your interest



pgsql-admin by date

Next:From: Fujii MasaoDate: 2009-04-09 09:02:24
Subject: Re: log_statements = mod or all
Previous:From: Daniel Cristian CruzDate: 2009-04-08 20:02:57
Subject: Re: Problem with table lock within a function

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group