From: Ed L. <pgsql@bluepolka.net>
To: pgsql-general@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: George Pavlov <gpavlov@mynewplace.com>
Subject: Re: query log corrupted-looking entries
Date: Fri, 1 Jun 2007 16:07:25 -0600
Message-ID: <200706011607.25894.pgsql@bluepolka.net> (raw)
In-Reply-To: <24195.1180733773@sss.pgh.pa.us>
References: <29860.1161202644@sss.pgh.pa.us>
<8C5B026B51B6854CBE88121DBF097A86CDD9A4@ehost010-33.exch010.intermedia.net>
<24195.1180733773@sss.pgh.pa.us>
On Friday 01 June 2007 3:36 pm, Tom Lane wrote:
> What *exactly* is the logging setup you guys use, and have you
> tried alternatives?
redirect_stderr = on # Enable capturing of stderr into log
log_directory = '/users/.../logs' # Directory where log files are written
log_filename = 'server_log.%a.%H:00-%H:59' # Log file name pattern.
log_truncate_on_rotation = on # If on, any existing log file of the same
log_rotation_age = 60min # Automatic rotation of logfiles will
log_min_messages = notice # Values, in order of decreasing detail:
log_connections = on
log_disconnections = on
log_duration = on
log_line_prefix = '%m [%p] %u %r %d ' # Special values:
log_statement = 'all' # none, ddl, mod, all
I have not tried alternatives. The status quo is adequate.
Ed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: pgsql@bluepolka.net, pgsql-general@postgresql.org, tgl@sss.pgh.pa.us, gpavlov@mynewplace.com
Subject: Re: query log corrupted-looking entries
In-Reply-To: <200706011607.25894.pgsql@bluepolka.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox