X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id E59D19DCAAD for ; Thu, 22 Dec 2005 12:53:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 13958-08 for ; Thu, 22 Dec 2005 12:53:09 -0400 (AST) 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 6B6619DC875 for ; Thu, 22 Dec 2005 12:53:08 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jBMGr1eX023604; Thu, 22 Dec 2005 11:53:02 -0500 (EST) To: "Dan Austin" cc: pgsql-admin@postgresql.org Subject: Re: Pgstat.tmp file activity In-reply-to: References: Comments: In-reply-to "Dan Austin" message dated "Thu, 22 Dec 2005 18:24:31 +1100" Date: Thu, 22 Dec 2005 11:53:01 -0500 Message-ID: <23603.1135270381@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.033 required=5 tests=[AWL=0.033] X-Spam-Score: 0.033 X-Spam-Level: X-Archive-Number: 200512/276 X-Sequence-Number: 19996 "Dan Austin" writes: > Solaris 10 has a tool called dtrace which reveals that pid #687 (a > postgres backend) is doing a LOT of writing to a single file (iosnoop.d > for you dtrace hackers): > UID PID D BLOCK SIZE COMM PATHNAME > 103 687 W 120384 98304 postgres > /export/data/pgsql/data/global/pgstat.tmp.687 Hmm. That's the stats collector creating a new current-stats file, which it does every half second or so. You might think about disabling stats collection if you don't have a need for it. But I'm having a hard time believing that that's the main cause of your bottleneck. The backends aren't supposed to block waiting for the stats collector ... regards, tom lane