Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: gprof SELECT COUNT(*) results
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
- Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: gprof SELECT COUNT(*) results
- Date: Sat, 26 Nov 2005 11:53:21 -0500
- Message-id: <3903(dot)1133024001(at)sss(dot)pgh(dot)pa(dot)us>
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes: >> ...and for emphasis: this optimization of SeqScans is not possible with >> any other database system, so its a big win for PostgreSQL. > With any other db system? That's a big call. Why? One could equally well spin it negatively, as "this optimization is not needed with any other database" ... regards, tom lane
- Follow-Ups:
- Re: gprof SELECT COUNT(*) results
- From: Simon Riggs
- 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
- Re: gprof SELECT COUNT(*) results
- From: Simon Riggs
- Re: gprof SELECT COUNT(*) results
- From: Christopher Kings-Lynne
- gprof SELECT COUNT(*) results
- Prev by Date: Re: SHOW ALL output too wide
- Next by Date: Re: gprof SELECT COUNT(*) results
- Previous by thread: Re: gprof SELECT COUNT(*) results
- Next by thread: Re: gprof SELECT COUNT(*) results
- Indexes: