From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "George Pavlov" <gpavlov(at)mynewplace(dot)com> |
Cc: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: query log corrupted-looking entries |
Date: | 2007-06-01 21:36:13 |
Message-ID: | 24195.1180733773@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"George Pavlov" <gpavlov(at)mynewplace(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tyler Durden | 2007-06-01 21:38:12 | Re: Seq Scan |
Previous Message | Andrew Sullivan | 2007-06-01 21:31:20 | Re: Slightly OT. |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-06-01 21:44:34 | Re: syslogger line-end processing infelicity |
Previous Message | Tom Lane | 2007-06-01 21:33:31 | Re: syslogger line-end processing infelicity |