From: Tom Lane <tgl@sss.pgh.pa.us>
To: George Pavlov <gpavlov@mynewplace.com>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: [GENERAL] query log corrupted-looking entries
Date: Wed, 18 Oct 2006 16:35:31 -0400
Message-ID: <165.1161203731@sss.pgh.pa.us> (raw)
In-Reply-To: <8C5B026B51B6854CBE88121DBF097A8651DFEF@ehost010-33.exch010.intermedia.net>
References: <8C5B026B51B6854CBE88121DBF097A8651DFEF@ehost010-33.exch010.intermedia.net>
"George Pavlov" <gpavlov@mynewplace.com> writes:
>> It'd be interesting to verify whether it's the same on
>> George's machine though.
> Let me know how to test this.
Identify the PID of one of your active backends (from "ps" or by looking
in pg_stat_activity), and then run
strace -p backend-pid-here 2>tmpfile
You'll need to do that as either root or postgres. Let it run for a
minute or three, preferably long enough to capture some long log
messages being emitted by that backend. (Bonus points if you can
capture one that's actually intermixed with others in the log, but
that might take some luck.) Stop it with control-C whenever you get
bored, and then grep through the tmpfile for lines beginning "write(2,".
It should be pretty clear whether log messages are being sent as single
or multiple write() operations.
regards, tom lane
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: tgl@sss.pgh.pa.us, gpavlov@mynewplace.com
Subject: Re: [GENERAL] query log corrupted-looking entries
In-Reply-To: <165.1161203731@sss.pgh.pa.us>
* 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