From: Guillaume Lelarge <guillaume@lelarge.info>
To: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org Admin <pgsql-admin@postgresql.org>
Subject: Re: 8.3 Logging Question
Date: Thu, 24 Jan 2008 20:56:29 +0100
Message-ID: <4798ED6D.4080701@lelarge.info> (raw)
In-Reply-To: <1d219a6f0801241031p4faa7b3cr2260f97e76bc71e0@mail.gmail.com>
References: <1d219a6f0801241031p4faa7b3cr2260f97e76bc71e0@mail.gmail.com>
Chris Hoover wrote:
> I'm running PG 8.3rc2 to start testing it out, and really like how it is
> preforming for me so far. However, I have one question on the logging.
> I am trying to use syslog and csvlog to log all sql. This seems to work
> great except that for every log rotation postgres does, I get a .csv log
> file that grows and a 0 byte .log file. Since I'm not logging to
> stderr, why is the .log file being created, and how do I turn that off?
>
Yes, I have the same issue. I don't think you can do something to stop
this behaviour. postmaster process creates the directory if not present,
then tries to create a file in it, and finally launches the syslogger
subprocess. The file it creates is your .log file. I'm not sure why it
creates a .log file. Perhaps the postmaster process has no idea at this
time that the DBA wants csvlog files.
Anyways, you'll only have one .log file because rotation function takes
care of the log_destination.
> [...]
> log_destination = 'syslog,csvlog' # Valid values are
> combinations of
This is kind of strange. It should be syslog or csvlog. It shouldn't be
both of them. Or am I wrong ?
Regards.
--
Guillaume.
http://www.postgresqlfr.orghttp://dalibo.com
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-admin@postgresql.org
Cc: guillaume@lelarge.info, revoohc@gmail.com
Subject: Re: 8.3 Logging Question
In-Reply-To: <4798ED6D.4080701@lelarge.info>
* 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