Skip site navigation (1) Skip section navigation (2)

Re: switchover between index and sequential scans

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Abhijit Menon-Sen" <ams(at)oryx(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: switchover between index and sequential scans
Date: 2008-07-03 10:05:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
"Abhijit Menon-Sen" <ams(at)oryx(dot)com> writes:

>          ->  Index Scan using header_fields_message_key on header_fields  (cost=0.00..1126.73 rows=325 width=4) (actual time=9.003..12.330 rows=17 loops=75)
>                Index Cond: (header_fields.message = "outer".message)
>          ->  Seq Scan on header_fields  (cost=0.00..85706.78 rows=1811778 width=4) (actual time=22.505..29281.553 rows=1812184 loops=1)

It looks to me like it's overestimating the number of rows in the index scan
by 20x and it's overestimating the cost of random accesses by about 100%.
Combined it's overestimating the cost of the index scan by about 40x.

> This machine has only 512MB of RAM, and is running FreeBSD 5.4. It has
> shared_buffers=3072, effective_cache_size=25000, work_mem=sort_mem=2048.
> Changing the last two doesn't seem to have any effect on the plan.

You could try dramatically increasing effective_cache_size to try to convince
it that most of the random accesses are cached. Or you could reach for the
bigger hammer and reduce random_page_cost by about half.

Also, if this box is dedicated you could make use of more than 24M for shared
buffers. Probably something in the region 64M-128M if your database is large
enough to warrant it.

And increase the statistics target on header_fields and re-analyze?

  Gregory Stark
  Ask me about EnterpriseDB's RemoteDBA services!

In response to


pgsql-performance by date

Next:From: Mokhtari AmineDate: 2008-07-03 10:17:47
Subject: cursor/Fetch mechanisms under postgreSQL
Previous:From: Abhijit Menon-SenDate: 2008-07-03 07:59:00
Subject: switchover between index and sequential scans

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group