Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 7BF139FB2CC for ; Wed, 18 Oct 2006 17:35:41 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 24670-05 for ; Wed, 18 Oct 2006 17:35:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 970BD9FA6B2 for ; Wed, 18 Oct 2006 17:35:36 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k9IKZVsK000166; Wed, 18 Oct 2006 16:35:32 -0400 (EDT) To: "George Pavlov" cc: pgsql-hackers@postgreSQL.org Subject: Re: [GENERAL] query log corrupted-looking entries In-reply-to: <8C5B026B51B6854CBE88121DBF097A8651DFEF@ehost010-33.exch010.intermedia.net> References: <8C5B026B51B6854CBE88121DBF097A8651DFEF@ehost010-33.exch010.intermedia.net> Comments: In-reply-to "George Pavlov" message dated "Wed, 18 Oct 2006 13:22:52 -0700" Date: Wed, 18 Oct 2006 16:35:31 -0400 Message-ID: <165.1161203731@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.088 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200610/1004 X-Sequence-Number: 92901 "George Pavlov" 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