From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | George Pavlov <gpavlov(at)mynewplace(dot)com>, "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: query log corrupted-looking entries |
Date: | 2007-06-08 01:32:01 |
Message-ID: | 20070608013201.GD20828@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> "George Pavlov" <gpavlov(at)mynewplace(dot)com> writes:
> > I tried the patch and it has no effect whatsoever -- even with the
> > patch, under the correct load the corrupted entries are coming fast and
> > furious (I found a load profile on my app that reproduces these very
> > clearly).
>
> What are the total lengths of the log entries in which you see the
> failure? (The "length" here includes all the lines belonging to a
> single logical entry, eg, ERROR, DETAIL, HINT.)
>
> I believe that this shouldn't be happening except in the case in which
> the entry-interpolated-into exceeds PIPE_BUF bytes. I'm not entirely
> sure what PIPE_BUF is on Linux machines, but IIRC the Posix spec says it
> has to be at least 512, and on older Unix kernels it tends to be 8K.
4096, although for some archs it may be bigger (it's the page size).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Guy Rouillier | 2007-06-08 02:00:59 | Re: Creditcard Number Security was Re: Encrypted column |
Previous Message | Alvaro Herrera | 2007-06-08 01:25:08 | Re: Creditcard Number Security was Re: Encrypted column |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2007-06-08 02:04:54 | Re: [COMMITTERS] pgsql: Avoid losing track of data for shared tables in pgstats. |
Previous Message | Tom Lane | 2007-06-08 01:19:50 | Re: .conf File Organization WAS: Controlling Load Distributed Checkpoints |