From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig Ringer <craig@postnewspapers.com.au>
Cc: Peter Schuller <peter.schuller@infidyne.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Identifying the nature of blocking I/O
Date: Sun, 24 Aug 2008 21:37:07 -0400
Message-ID: <866.1219628227@sss.pgh.pa.us> (raw)
In-Reply-To: <48B1FD1A.7040807@postnewspapers.com.au>
References: <20080822115243.GA10981@hyperion.scode.org>
<48B1FD1A.7040807@postnewspapers.com.au>
Craig Ringer <craig@postnewspapers.com.au> 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.
<cant-resist>get a mac</cant-resist>
(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
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, craig@postnewspapers.com.au, peter.schuller@infidyne.com
Subject: Re: Identifying the nature of blocking I/O
In-Reply-To: <866.1219628227@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