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

Re: query log corrupted-looking entries

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "George Pavlov" <gpavlov(at)mynewplace(dot)com>
Subject: Re: query log corrupted-looking entries
Date: 2007-06-01 22:07:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
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.


In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-06-01 22:07:41
Subject: Re: syslogger line-end processing infelicity
Previous:From: Ed L.Date: 2007-06-01 22:03:21
Subject: Re: query log corrupted-looking entries

pgsql-general by date

Next:From: Scott RibeDate: 2007-06-01 22:08:04
Subject: Re: Slightly OT.
Previous:From: Alexander StauboDate: 2007-06-01 22:05:20
Subject: Re: Slightly OT.

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