Re: index vs. seq scan choice?

From: ptjm(at)interlog(dot)com (Patrick TJ McPhee)
To: pgsql-general(at)postgresql(dot)org
Subject: Re: index vs. seq scan choice?
Date: 2007-06-08 04:13:54
Message-ID: 136hls2op53c285@corp.supernews.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-www

In article <415(dot)1181255628(at)sss(dot)pgh(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
% "George Pavlov" <gpavlov(at)mynewplace(dot)com> writes:
% >> From: Joshua D. Drake [mailto:jd(at)commandprompt(dot)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.

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

Patrick TJ McPhee
North York Canada
ptjm(at)interlog(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John Meyer 2007-06-08 04:45:00 Re: [SQL] subtract a day from the NOW function
Previous Message Tom Lane 2007-06-08 04:12:10 Re: [SQL] subtract a day from the NOW function

Browse pgsql-www by date

  From Date Subject
Next Message Kevin Hunter 2007-06-08 11:56:33 Re: [DOCS] Users comments don't migrate to docs for new version?
Previous Message Andrej Ricnik-Bay 2007-06-07 23:24:09 Re: [pgsql-www] Users comments don't migrate to docs for new version?