From: Jonah H. Harris <jonah.harris@gmail.com>
To: Peter Schuller <peter.schuller@infidyne.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Identifying the nature of blocking I/O
Date: Mon, 25 Aug 2008 10:20:37 -0400
Message-ID: <36e682920808250720p2931727cif70447be301bd71c@mail.gmail.com> (raw)
In-Reply-To: <20080822115243.GA10981@hyperion.scode.org>
References: <20080822115243.GA10981@hyperion.scode.org>
On Fri, Aug 22, 2008 at 7:52 AM, Peter Schuller
<peter.schuller@infidyne.com> wrote:
> Is there currently a way of dumping such information? I.e., asking PG
> "what are backends waiting on right now?".
Unfortunately, not within Postgres itself. The question, "what is the
database waiting on?" is a good one, and one Oracle understood in the
early 90's. It is for that reason that EnterpriseDB added RITA, the
Runtime Instrumentation and Tracing Architecture, to their Advanced
Server product. RITA gives DBAs some of the same information as the
Oracle Wait Interface does regarding what the database is waiting for,
such as locks, I/O, and which relation/block. While it's not as
efficient as DTrace due to Linux's lack of a good high-resolution
user-mode timer, no one has found it to have a noticible overhead on
the throughput of a system in benchmarks or real-world applications.
If you're on a DTrace platform, I would suggest using it. Otherwise,
you can try and use strace/ltrace on Linux, but that's probably not
going to get you the answers you need quickly or easily enough. Until
enough users ask for this type of feature, the community isn't going
to see it as valuable enough to add to the core engine. IIRC,
systemtap is pretty much dead :(
--
Jonah H. Harris, Senior DBA
myYearbook.com
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: jonah.harris@gmail.com, peter.schuller@infidyne.com
Subject: Re: Identifying the nature of blocking I/O
In-Reply-To: <36e682920808250720p2931727cif70447be301bd71c@mail.gmail.com>
* 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