Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: gprof SELECT COUNT(*) results
- From: Simon Riggs <simon(at)2ndquadrant(dot)com>
- To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: gprof SELECT COUNT(*) results
- Date: Sat, 26 Nov 2005 12:39:21 +0000
- Message-id: <1133008761(dot)2906(dot)121(dot)camel(at)localhost(dot)localdomain>
On Sat, 2005-11-26 at 03:13 -0500, Qingqing Zhou wrote: > "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote > > > > I plan to take a look at it soon. > > > > "Stand corrected"[Merlin]! In-memory "SELECT COUNT(*)" doubles the > performance due to my test. > > - before - > 1.56 s > > - now - > 0.72 s > ...and for emphasis: this optimization of SeqScans is not possible with any other database system, so its a big win for PostgreSQL. Best Regards, Simon Riggs
- Follow-Ups:
- Re: gprof SELECT COUNT(*) results
- From: Christopher Kings-Lynne
- Re: gprof SELECT COUNT(*) results
- References:
- gprof SELECT COUNT(*) results
- From: Qingqing Zhou
- Re: gprof SELECT COUNT(*) results
- From: Simon Riggs
- Re: gprof SELECT COUNT(*) results
- From: Qingqing Zhou
- Re: gprof SELECT COUNT(*) results
- From: Tom Lane
- Re: gprof SELECT COUNT(*) results
- From: Simon Riggs
- Re: gprof SELECT COUNT(*) results
- From: Tom Lane
- Re: gprof SELECT COUNT(*) results
- From: Qingqing Zhou
- gprof SELECT COUNT(*) results
- Prev by Date: Re: plpython and bytea
- Next by Date: Re: SHOW ALL output too wide
- Previous by thread: Re: gprof SELECT COUNT(*) results
- Next by thread: Re: gprof SELECT COUNT(*) results
- Indexes: