From: | Viktor Rosenfeld <listuser36(at)googlemail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: different execution times of the same query |
Date: | 2009-10-20 15:40:14 |
Message-ID: | 20091020154014.GC1696@stan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I suppose the same is true for the time logged with log_duration, i.e.
it does not include the time needed to transfer the data to the client?
Or is it more like \timing in that respect?
Cheers,
Viktor
Craig Ringer wrote:
> EXPLAIN ANALYZE measures the time taken to execute the query. It doesn't
> include time required to transfer results to the client, possibly write
> them to disk, etc. It's really only for examining query plans as
> compared to actual execution of that plan.
>
> If you're more interested in *total* query execution time, including
> planning, execution, and transfer of results, you should usually use
> psql's \timing command, possibly along with output redirection. eg:
From | Date | Subject | |
---|---|---|---|
Next Message | Sim Zacks | 2009-10-20 15:40:16 | Re: cast numeric with scale and precision to numeric plain |
Previous Message | Grzegorz Jaśkiewicz | 2009-10-20 15:34:00 | Re: Sharedbuffers and WorkMem |