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

Re: query log corrupted-looking entries

From: "George Pavlov" <gpavlov(at)mynewplace(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-02 18:32:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
> "George Pavlov" <gpavlov(at)mynewplace(dot)com> writes:
> > ... Also redirect_stderr = on.
> Hm.  Well, that's the bit that ought to get you into the PIPE_BUF
> exception.  There's been some speculation that a change like the
> attached would help.  I've found that it makes no difference with
> my libc, but maybe yours is different --- want to try it?

I will. I may need some time though, since I first need to find a way to
reproduce the problem reliably on my test environments and right now I
cannot seem to. I have seen the problem mostly under production loads
(also under certain kinds of stress-testing, but I forget exactly which

In the meantime I went and looked at the logs in more detail and the
corrupted entries seem much more prevalent than what I originally
thought. Apart from the ones pgfouine complains about there are many
more such lines. For example out of a (average-load) day's log file with
17+ million lines pgfouine complains about 8 lines, but there are in
fact 1400+ lines with these kinds of entries.


In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-06-02 20:05:48
Subject: Tsearch vs Snowball, or what's a source file?
Previous:From: Josh BerkusDate: 2007-06-02 17:33:06
Subject: Re: To all the pgsql developers..Have a look at the operators proposed by me in my research paper.

pgsql-general by date

Next:From: Andrew SullivanDate: 2007-06-02 18:35:11
Subject: Re: One last Slony question (was Re: Slightly OT.)
Previous:From: Sergei ShelukhinDate: 2007-06-02 18:08:18
Subject: insane index scan times

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