| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Cc: | "Joost Kraaijeveld" <J(dot)Kraaijeveld(at)Askesis(dot)nl> |
| Subject: | Re: Measuring server performance with psql and pgAdmin |
| Date: | 2004-10-26 19:20:21 |
| Message-ID: | 200410261220.21435.josh@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Joost,
> 1. The manual says about "explain analyze" : "The ANALYZE option causes the
> statement to be actually executed, not only planned. The total elapsed time
> expended within each plan node (in milliseconds) and total number of rows
> it actually returned are added to the display." Does this time include
> datatransfer or just the time the database needs to collect the data,
> without any data transfer?
Correct. It's strictly backend time.
> 2. If the time is without data transfer to the
> client, is there a reliable way to measure the time needed to run the query
> and get the data (without the overhead of a program that does something
> with the data)?
in PSQL, you can use \timing
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2004-10-26 20:19:06 | Re: Sequential Scan with LIMIT |
| Previous Message | Matt Clark | 2004-10-26 18:28:34 | Re: can't handle large number of INSERT/UPDATEs |