Skip site navigation (1) Skip section navigation (2)

Re: EXPLAIN ANALYZE printing logical and hardware I/O per-node

From: Robert Lor <Robert(dot)Lor(at)Sun(dot)COM>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Decibel! <decibel(at)decibel(dot)org>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: EXPLAIN ANALYZE printing logical and hardware I/O per-node
Date: 2008-01-03 16:08:12
Message-ID: 477D086C.3080005@sun.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Greg,

Gregory Stark wrote:
> I don't think DTrace is overkill either. The programmatic interface is
> undocumented (but I've gotten Sun people to admit it exists -- I just have to
> reverse engineer it from the existing code samples) but should be more or less
> exactly what we need.
>
>   
You  probably know this already. There are existing commands that use 
the programmatic interface and would provide a good starting point. Here 
are a couple:

http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/lockstat/lockstat.c
http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/dtrace/dtrace.c

One of my colleagues is in the process of putting a tutorial together 
for how to do this, so if you decided to pursue this approach and need 
assistance, please let me know.

Regards,
Robert

In response to

pgsql-hackers by date

Next:From: Josh BerkusDate: 2008-01-03 22:53:56
Subject: Please submit for OSCON!
Previous:From: Andrew DunstanDate: 2008-01-03 15:57:51
Subject: Re: Table rewrites vs. pending AFTER triggers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group