From: | Jessica Blank <jb(at)twu(dot)net> |
---|---|
To: | Justin Clift <justin(at)postgresql(dot)org> |
Cc: | Joe Conway <mail(at)joeconway(dot)com>, "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Measuring CPU time use? (Another stupid question) |
Date: | 2002-12-18 22:36:57 |
Message-ID: | Pine.LNX.4.44.0212181536140.392-100000@ensim.rackshack.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bllllleleeeuuuughhh...
I'd rather not touch Red Hat's stuff.. or ANYTHING with "Explain" in the
name >G< Thank you for the info tho...
I would much rather just get the info via a simple command line, or a line
of SQL, or something I can do in Perl....
On Thu, 19 Dec 2002, Justin Clift wrote:
> Joe Conway wrote:
> > Jessica Blank wrote:
> >
> >> I suppose I should rephrase.
> > [...snip...]
> >> So I guess what I'm saying is that I don't care so much about CPU
> >> time, or I/O time, but *TOTAL* time. How long it takes from the
> >> instant the query hits Postgres to the instant I get my results back...
> >
> >
> > That's pretty much exactly what EXPLAIN ANALYZE does for you. And along
> > with it, you get other useful information to help you improve the query.
>
> Red Hat recently released their "Visual Explain 1.1" tool as well, and that looks like it could be very useful for what
> Jessica's after too:
>
> http://sources.redhat.com/rhdb/tools.html
>
> :-)
>
> Regards and best wishes,
>
> Justin Clift
>
>
> > Joe
>
>
>
>
--
J e s s i c a L e a h B l a n k
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2002-12-18 22:51:39 | Re: trouble caused by change in 7.3 handling of '' in |
Previous Message | Bruce Momjian | 2002-12-18 22:28:37 | Re: trouble caused by change in 7.3 handling of '' in |