From: | Lewis Cunningham <lewisc(at)rocketmail(dot)com> |
---|---|
To: | "korry(dot)douglas" <korry(dot)douglas(at)enterprisedb(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Procedural Code Profiling |
Date: | 2007-08-06 19:31:09 |
Message-ID: | 537429.62801.qm@web35606.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
--- "korry.douglas" <korry(dot)douglas(at)enterprisedb(dot)com> wrote:
> execution count (number of times each statement is executed)
> total execution time (how long did we spend executing each
> statement?)
> longest execution time (how long did the slowest iteration
> take?)
> number of scans (total number of sequential and indexed scans)
> blocks fetched (for each statement)
> blocks hit (blocks found in buffer pool) (for each statement)
> tuples returned (for each statement)
> tuples fetched (for each statement)
> tuples inserted (for each statement)
> tuples updated (for each statement)
> tuples deleted (for each statement)
>
Sweet. This is exactly what I was looking for.
Thanks,
LewisC
-----------------------------------------------------------
Lewis R Cunningham
An Expert's Guide to Oracle Technology
http://blogs.ittoolbox.com/oracle/guide/
LewisC's Random Thoughts
http://lewiscsrandomthoughts.blogspot.com/
EnterpriseDB: The Definitive Reference
http://tinyurl.com/39246e
----------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Ed L. | 2007-08-06 19:36:33 | Re: 8.1.2 select for update issue |
Previous Message | Stuart | 2007-08-06 19:30:41 | dbi and indexes |