Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B2E6B65014C for ; Sun, 24 Aug 2008 22:37:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 34758-01 for ; Sun, 24 Aug 2008 22:37:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 43910650136 for ; Sun, 24 Aug 2008 22:37:17 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m7P1b8D2000867; Sun, 24 Aug 2008 21:37:08 -0400 (EDT) To: Craig Ringer cc: Peter Schuller , pgsql-performance@postgresql.org Subject: Re: Identifying the nature of blocking I/O In-reply-to: <48B1FD1A.7040807@postnewspapers.com.au> References: <20080822115243.GA10981@hyperion.scode.org> <48B1FD1A.7040807@postnewspapers.com.au> Comments: In-reply-to Craig Ringer message dated "Mon, 25 Aug 2008 08:30:18 +0800" Date: Sun, 24 Aug 2008 21:37:07 -0400 Message-ID: <866.1219628227@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/316 X-Sequence-Number: 31197 Craig Ringer writes: > Peter Schuller wrote: >> But in general, it would be very interesting to see, at any given >> moment, what PostgreSQL backends are actually blocking on from the >> perspective of PostgreSQL. > The recent work on DTrace support for PostgreSQL will probably give you > the easiest path to useful results. You'll probably need an OpenSolaris > or (I think) FreeBSD host, though, rather than a Linux host. get a mac (Mind you, I don't think Apple sells any hardware that would be really suitable for a big-ass database server. But for development purposes, OS X on a recent laptop is a pretty nice unix-at-the-core-plus-eye-candy environment.) regards, tom lane