Re: Much Ado About COUNT(*) - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: Much Ado About COUNT(*)
Date
Msg-id 41E58BD2.70604@tvi.edu
Whole thread Raw
In response to Re: Much Ado About COUNT(*)  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: Much Ado About COUNT(*)  (Jon Jensen <jon@endpoint.com>)
Re: Much Ado About COUNT(*)  (Bruno Wolff III <bruno@wolff.to>)
Re: Much Ado About COUNT(*)  (Jeff Davis <jdavis-pgsql@empires.org>)
Re: Much Ado About COUNT(*)  (Sailesh Krishnamurthy <sailesh@cs.berkeley.edu>)
List pgsql-hackers
Andrew Dunstan wrote:

>Monetary cost is not the issue - cost in time is the issue.
>
>cheers
>
>andrew
>  
>
We seem to be in agreement.  I'm looking for faster/smarter access to 
data, not the monetary cost of doing so.  Isn't it faster/smarter to 
satisfy a query with the index rather than sequentially scanning an 
entire relation if it is possible?

Replying to the list as a whole:

If this is such a bad idea, why do other database systems use it?  As a 
businessperson myself, it doesn't seem logical to me that commercial 
database companies would spend money on implementing this feature if it 
wouldn't be used.  Remember guys, I'm just trying to help.



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Much Ado About COUNT(*)
Next
From: "Jim Buttafuoco"
Date:
Subject: PANIC: right sibling's left-link doesn't match