From: Pavan Deolasee <pavan.deolasee@gmail.com>
To: Luigi N. Puleio <npuleio@rocketmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: EXPLAIN detail
Date: Wed, 9 Apr 2008 15:34:06 +0530
Message-ID: <2e78013d0804090304l611044d6q4a71a927ec199b65@mail.gmail.com> (raw)
In-Reply-To: <862313.90586.qm@web33505.mail.mud.yahoo.com>
References: <862313.90586.qm@web33505.mail.mud.yahoo.com>
On Wed, Apr 9, 2008 at 3:21 PM, Luigi N. Puleio <npuleio@rocketmail.com> wrote:
> Hello everyone!!
>
> I have a table with 17 columns and it has almost
> 530000 records and doing just a
>
> SELECT * FROM table
>
> with the EXPLAIN ANALYZE I get:
>
> Seq Scan on table (cost=0.00...19452.95 rows=529395
> width=170) (actual time=0.155...2194.294 rows=529395
> loops=1)
> total runtime=3679.039 ms
>
> and this table has a PK...
> Do you think is too much time for a simple select?...
>
Well, PK won't help you here because you are selecting all rows
from the table and that seq scan is the right thing for that.
Without knowing your hardware its difficult to judge if
the time taken is more or not. Anyways, I don't think there is much
tweaking you can do for such a query except making sure that
your table is not bloated with dead tuples.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
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: pavan.deolasee@gmail.com, npuleio@rocketmail.com
Subject: Re: EXPLAIN detail
In-Reply-To: <2e78013d0804090304l611044d6q4a71a927ec199b65@mail.gmail.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