Re: Tracing I/O (was: 8.1 and syntax checking at create time) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Tracing I/O (was: 8.1 and syntax checking at create time)
Date
Msg-id 20050902022653.GA1120@surnet.cl
Whole thread Raw
In response to Tracing I/O (was: 8.1 and syntax checking at create time)  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
On Thu, Sep 01, 2005 at 09:06:29PM -0500, Jim C. Nasby wrote:
> On Wed, Aug 31, 2005 at 04:08:10PM -0400, huaxin zhang wrote:
> > I am new to this hacker's job. What I was looking for was to record
> > the actual disk IO performed for arbituary query plan. I searched
> > in backend/executor but not sure if that was the right place to 
> > add a tracer. would the /backend/storage be the place that controls
> > the actual I/O? btw, is there a way to find the definitions of all variables
> > or functions defined? I tried cscope but it is not good for such a large 
> > framework.
> >  thanks a lot
> 
> I believe you'd want backend/storage, but I'm just guessing.

backend/storage/smgr/md.c

-- 
Alvaro Herrera -- Valdivia, Chile         Architect, www.EnterpriseDB.com
"Sallah, I said NO camels! That's FIVE camels; can't you count?"
(Indiana Jones)


pgsql-hackers by date:

Previous
From: "Matthew Miller"
Date:
Subject: Re: PL/pgSQL: EXCEPTION NOSAVEPOINT
Next
From: "Jim C. Nasby"
Date:
Subject: Additional background daemon (was: Remove xmin and cmin from frozen tuples)