Re: Seq Scan vs. Index Scan - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: Seq Scan vs. Index Scan
Date
Msg-id 4E3A6F6E020000250003FA53@gw.wicourts.gov
Whole thread Raw
In response to Seq Scan vs. Index Scan  (Nassib Nassar <nassar@renci.org>)
List pgsql-performance
Nassib Nassar <nassar@renci.org> wrote:

> In this example it looks to me like the planner is choosing a Seq
> Scan resulting in 18x running time compared to running it with
> enable_seqscan = 'off'.

I would try these settings:

random_page_cost = 2
cpu_tuple_cost = 0.02

Based on your estimated cost versus actual run times, there's a good
chance they'll better model your environment, and serve you well in
general.

-Kevin

pgsql-performance by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Need to tune for Heavy Write
Next
From: "Kevin Grittner"
Date:
Subject: Re: Performance die when COPYing to table with bigint PK