From: Ed L. <pgsql@bluepolka.net>
To: George Pavlov <gpavlov@mynewplace.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@postgresql.org, "Alvaro Herrera" <alvherre@commandprompt.com>
Subject: Re: query log corrupted-looking entries
Date: Fri, 8 Jun 2007 10:34:24 -0600
Message-ID: <200706081034.24774.pgsql@bluepolka.net> (raw)
In-Reply-To: <8C5B026B51B6854CBE88121DBF097A86DEA7AE@ehost010-33.exch010.intermedia.net>
References: <29860.1161202644@sss.pgh.pa.us>
<11458.1181265461@sss.pgh.pa.us>
<8C5B026B51B6854CBE88121DBF097A86DEA7AE@ehost010-33.exch010.intermedia.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: pgsql@bluepolka.net, gpavlov@mynewplace.com, tgl@sss.pgh.pa.us, alvherre@commandprompt.com
Subject: Re: query log corrupted-looking entries
In-Reply-To: <200706081034.24774.pgsql@bluepolka.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox