Re: query log corrupted-looking entries

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 22:25:13
Message-ID: 24885.1180736713@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:
>> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]=20
>> What *exactly* is the logging setup you guys use, and have you tried
>> alternatives?

> ... 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?

regards, tom lane

Attachment Content-Type Size
unknown_filename text/plain 738 bytes

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2007-06-01 22:25:28 Re: Slightly OT.
Previous Message Guy Rouillier 2007-06-01 22:24:09 Re: multimaster

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-06-01 22:30:10 Re: syslogger line-end processing infelicity
Previous Message Zdenek Kotala 2007-06-01 22:20:06 Re: Command tags in create/drop scripts