From: Tom Lane <tgl@sss.pgh.pa.us>
To: George Pavlov <gpavlov@mynewplace.com>
Cc: Ed L. <pgsql@bluepolka.net>
Cc: pgsql-general@postgresql.org
Subject: Re: query log corrupted-looking entries
Date: Fri, 01 Jun 2007 17:36:13 -0400
Message-ID: <24195.1180733773@sss.pgh.pa.us> (raw)
In-Reply-To: <8C5B026B51B6854CBE88121DBF097A86CDD9A4@ehost010-33.exch010.intermedia.net>
References: <29860.1161202644@sss.pgh.pa.us>
<8C5B026B51B6854CBE88121DBF097A86C39FC2@ehost010-33.exch010.intermedia.net>
<200705291119.55567.pgsql@bluepolka.net>
<8C5B026B51B6854CBE88121DBF097A86CDD9A4@ehost010-33.exch010.intermedia.net>
"George Pavlov" <gpavlov@mynewplace.com> writes:
> On 5/29/2007 10:19 AM, Ed L. wrote:
>> FWIW, I've also been seeing this sort of query log corruption for
>> as long as I can remember, 7.1 through 8.2, HPUX (parisc, ia64),
>> Linux on intel, amd...
What *exactly* is the logging setup you guys use, and have you tried
alternatives?
As best I can tell, the variant with a downstream syslogger process
ought to be OK for messages up to PIPEBUF bytes long on most standard
Unixen. Of course that's no help if you've got lots of very verbose
queries, but the examples posted so far didn't seem to indicate that.
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, gpavlov@mynewplace.com, pgsql@bluepolka.net, pgsql-general@postgresql.org
Subject: Re: query log corrupted-looking entries
In-Reply-To: <24195.1180733773@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