From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
---|---|
To: | "George Pavlov" <gpavlov(at)mynewplace(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
Subject: | Re: query log corrupted-looking entries |
Date: | 2007-06-08 16:34:24 |
Message-ID: | 200706081034.24774.pgsql@bluepolka.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Friday 08 June 2007 10:30 am, George Pavlov wrote:
>
> It is very hard to tease these apart because now that I look
> at it closely it is a total mess; there are multiple
> interruptions and interruptions inside of interruptions...
> The interruption can happen anywhere, including the leading
> log timestamp
This describes my experiences as well on our high-volume
clusters.
Ed
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2007-06-08 16:38:33 | Re: Limitations on 7.0.3? |
Previous Message | George Pavlov | 2007-06-08 16:30:21 | Re: query log corrupted-looking entries |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2007-06-08 17:21:37 | Re: query log corrupted-looking entries |
Previous Message | George Pavlov | 2007-06-08 16:30:21 | Re: query log corrupted-looking entries |