| From: | Ants Aasma <ants(dot)aasma(at)eesti(dot)ee> |
|---|---|
| To: | kelphet xiong <kelphet(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Question about postmaster's CPU usage |
| Date: | 2013-03-30 23:45:31 |
| Message-ID: | CA+CSw_t-qvn3fj_6QYE+TK3150pfLdDqO87wnP8fZPfVNm8C9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mar 28, 2013 9:07 PM, "kelphet xiong" <kelphet(at)gmail(dot)com> wrote:
> explain analyze select * from inventory;
> QUERY PLAN
>
>
--------------------------------------------------------------------------------------------------------------
> ------------
> Seq Scan on inventory (cost=0.00..180937.00 rows=11745000 width=16)
(actual time=0.005..1030.403 rows=117450
> 00 loops=1)
> Total runtime: 1750.889 ms
> (2 rows)
A large fraction of that time, if not most is due to timing overhead. You
can try the same query without timing by using explain (analyze on, timing
off) select * from inventory;
Regards,
Ants Aasma
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kelphet Xiong | 2013-03-31 04:00:02 | Re: Question about postmaster's CPU usage |
| Previous Message | Jeff Janes | 2013-03-30 19:00:58 | Re: Postgresql performance degrading... how to diagnose the root cause |