| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Identifying the nature of blocking I/O |
| Date: | 2008-08-25 01:37:07 |
| Message-ID: | 866.1219628227@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Craig Ringer <craig(at)postnewspapers(dot)com(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-25 01:49:51 | Re: Identifying the nature of blocking I/O |
| Previous Message | Scott Carey | 2008-08-25 01:34:18 | Re: Identifying the nature of blocking I/O |