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

Re: query log corrupted-looking entries

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "George Pavlov" <gpavlov(at)mynewplace(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: query log corrupted-looking entries
Date: 2007-06-01 22:03:21
Message-ID: 200706011603.21322.pgsql@bluepolka.net (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
On Friday 01 June 2007 3:36 pm, Tom Lane wrote:
> "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.

On older versions, we use stderr piped to Apache's rotatelogs.  
On newer versions with built-in logging, we use it.  We do have 
considerably verbose queries (sometimes a page or so).  No idea 
what PIPEBUF equals.

Ed

In response to

pgsql-hackers by date

Next:From: Ed L.Date: 2007-06-01 22:07:25
Subject: Re: query log corrupted-looking entries
Previous:From: George PavlovDate: 2007-06-01 21:55:41
Subject: Re: query log corrupted-looking entries

pgsql-general by date

Next:From: Alexander StauboDate: 2007-06-01 22:05:20
Subject: Re: Slightly OT.
Previous:From: Joshua D. DrakeDate: 2007-06-01 22:03:10
Subject: Re: New Live CD needed

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