Search Postgresql Archives

Re: index vs. seq scan choice?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In article <415.1181255628@xxxxxxxxxxxxx>, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
% "George Pavlov" <gpavlov@xxxxxxxxxxxxxx> writes:
% >> From: Joshua D. Drake [mailto:jd@xxxxxxxxxxxxxxxxx]
% >> 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.

Also, increasing effective_cache_size.
(And increasing statistics...)
-- 

Patrick TJ McPhee
North York  Canada
ptjm@xxxxxxxxxxxx


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux