Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E8BF52E003C for ; Tue, 25 Mar 2008 10:34:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 54106-05 for ; Tue, 25 Mar 2008 10:34:30 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by postgresql.org (Postfix) with ESMTP id F00D42E003B for ; Tue, 25 Mar 2008 10:34:38 -0300 (ADT) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (vanquish.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.162]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Tue, 25 Mar 2008 09:34:39 -0400 id 00056416.47E8FF6F.0000FAF4 Date: Tue, 25 Mar 2008 09:34:40 -0400 From: Bill Moran To: "sathiya psql" Cc: "Craig Ringer" , pgsql-performance@postgresql.org Subject: Re: what is the maximum number of rows in a table in postgresql 8.1 Message-Id: <20080325093440.1bcd47e1.wmoran@collaborativefusion.com> In-Reply-To: References: <7be3f35d0803250448h62f47b13mebe0252fca9b90e1@mail.gmail.com> <20080325120101.GC6756@alvh.no-ip.org> <47E8EEF1.40709@postnewspapers.com.au> Organization: Collaborative Fusion X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.8; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/476 X-Sequence-Number: 29430 In response to "sathiya psql" : > EXPLAIN ANALYZE SELECT count(*) from call_log_in_ram ; > QUERY > PLAN > ---------------------------------------------------------------------------------------------------------------------------------- > Aggregate (cost=90760.80..90760.80 rows=1 width=0) (actual time= > 6069.373..6069.374 rows=1 loops=1) > -> Seq Scan on call_log_in_ram (cost=0.00..89121.24 rows=3279119 > width=0) (actual time=0.012..4322.345 rows=3279119 loops=1) > Total runtime: 6069.553 ms > (3 rows) > > zivah=# EXPLAIN ANALYZE SELECT count(*) from call_log_in_ram ; > QUERY > PLAN > ---------------------------------------------------------------------------------------------------------------------------------- > Aggregate (cost=90760.80..90760.80 rows=1 width=0) (actual time= > 6259.436..6259.437 rows=1 loops=1) > -> Seq Scan on call_log_in_ram (cost=0.00..89121.24 rows=3279119 > width=0) (actual time=0.013..4448.549 rows=3279119 loops=1) > Total runtime: 6259.543 ms 6 seconds doesn't sound like an unreasonable amount of time to count 3 million rows. I don't see any performance issue here. What were your expectations? -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@collaborativefusion.com Phone: 412-422-3463x4023