Re: EXPLAIN detail

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: EXPLAIN detail
Дата
Msg-id 2e78013d0804090304l611044d6q4a71a927ec199b65@mail.gmail.com
обсуждение исходный текст
Ответ на EXPLAIN detail  ("Luigi N. Puleio" <npuleio@rocketmail.com>)
Ответы Re: EXPLAIN detail  (Craig Ringer <craig@postnewspapers.com.au>)
Re: EXPLAIN detail  (Matthew <matthew@flymine.org>)
Re: EXPLAIN detail  ("Luigi N. Puleio" <npuleio@rocketmail.com>)
Список pgsql-performance
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

В списке pgsql-performance по дате отправления:

Предыдущее
От: "Luigi N. Puleio"
Дата:
Сообщение: EXPLAIN detail
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: EXPLAIN detail