From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Major Problems with PostgreSQL Logs (8.1.3)
Date: Fri, 09 Jun 2006 17:01:37 -0400
Message-ID: <24760.1149886897@sss.pgh.pa.us> (raw)
In-Reply-To: <1d219a6f0606091027w554c5b66o38b2ecce5d2ec8f6@mail.gmail.com>
References: <1d219a6f0606091027w554c5b66o38b2ecce5d2ec8f6@mail.gmail.com>
"Chris Hoover" <revoohc@gmail.com> writes:
> ---I am having a major problem with the PostgreSQL log files. We have sql
> logging turned on for recovery purposes, and have discovered a problem. We
> have lines of sql being interrupted by the next log line before they
> complete. The interrupting log line is not starting at the beginning of a
> line, but rather cutting right into the middle of the previous log line.
> Eventually, the intrrupted log line is completed. This is causing serious
> issues for us, since we can not rely on the log files to be accurrate.
You might try using syslog logging, although I'm not sure whether it
would really be much better. If your log messages exceed PIPEBUF (8K
typically) then writes to the redirect_stderr process are not going to
be atomic, and there's not all that much we can do about it.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, revoohc@gmail.com
Subject: Re: Major Problems with PostgreSQL Logs (8.1.3)
In-Reply-To: <24760.1149886897@sss.pgh.pa.us>
References: <1d219a6f0606091027w554c5b66o38b2ecce5d2ec8f6@mail.gmail.com> <24760.1149886897@sss.pgh.pa.us>
* 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