pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bill Moran <wmoran@collaborativefusion.com>
To: sathiya psql <sathiya.psql@gmail.com>
Cc: Craig Ringer <craig@postnewspapers.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: what is the maximum number of rows in a table in postgresql 8.1
Date: Tue, 25 Mar 2008 09:34:40 -0400
Message-ID: <20080325093440.1bcd47e1.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <f966c2ee0803250550o563309a3p2c2d4509535c8bf6@mail.gmail.com>
References: <f966c2ee0803250442g9ceaf61v2c3f35221fcc6481@mail.gmail.com>
	<7be3f35d0803250448h62f47b13mebe0252fca9b90e1@mail.gmail.com>
	<f966c2ee0803250454k716edf4cgcd054e7b563e530c@mail.gmail.com>
	<20080325120101.GC6756@alvh.no-ip.org>
	<f966c2ee0803250508t444524b6y44b9ee67c8e04673@mail.gmail.com>
	<47E8EEF1.40709@postnewspapers.com.au>
	<f966c2ee0803250550o563309a3p2c2d4509535c8bf6@mail.gmail.com>

In response to "sathiya psql" <sathiya.psql@gmail.com>:

> 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



view thread (11+ messages)  latest in thread

Message-ID: <20080325093440.1bcd47e1.wmoran@collaborativefusion.com>
Permalink:  ../20080325093440.1bcd47e1.wmoran@collaborativefusion.com/
Also on:    postgresql.org/message-id/20080325093440.1bcd47e1.wmoran@collaborativefusion.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: wmoran@collaborativefusion.com, sathiya.psql@gmail.com, craig@postnewspapers.com.au
  Subject: Re: what is the maximum number of rows in a table in postgresql 8.1
  In-Reply-To: <20080325093440.1bcd47e1.wmoran@collaborativefusion.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox