Re: [GENERAL] 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: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [GENERAL] query log corrupted-looking entries
Date: 2006-10-18 20:35:31
Message-ID: 165.1161203731@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:
>> 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Browne 2006-10-18 20:36:20 Re: Stats Collector Won't Start
Previous Message Ron Johnson 2006-10-18 20:32:09 Re: Drop All the Databases

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2006-10-18 20:41:19 Re: Mirror problems for download
Previous Message George Pavlov 2006-10-18 20:22:52 Re: [GENERAL] query log corrupted-looking entries