Re: index vs. seq scan choice? - Mailing list pgsql-general

From Tom Lane
Subject Re: index vs. seq scan choice?
Date
Msg-id 415.1181255628@sss.pgh.pa.us
Whole thread Raw
In response to Re: index vs. seq scan choice?  ("George Pavlov" <gpavlov@mynewplace.com>)
Responses Re: index vs. seq scan choice?  ("George Pavlov" <gpavlov@mynewplace.com>)
List pgsql-general
"George Pavlov" <gpavlov@mynewplace.com> writes:
>> From: Joshua D. Drake [mailto:jd@commandprompt.com]
>> In those rare cases wouldn't it make more sense to just set
>> enable_seqscan to off; run query; set enable_seqscan to on;

> 1. these cases are not that rare (to me);

It strikes me that you probably need to adjust the planner cost
parameters to reflect reality on your system.  Usually dropping
random_page_cost is the way to bias the thing more in favor of
index scans.

            regards, tom lane

pgsql-general by date:

Previous
From: Rodrigo De León
Date:
Subject: Re: list all columns in db
Next
From: Jon Sime
Date:
Subject: Re: list all columns in db