In article <[EMAIL PROTECTED]>, Tom Lane <[EMAIL PROTECTED]> wrote:
% "George Pavlov" <[EMAIL PROTECTED]> writes:
% >> From: Joshua D. Drake [mailto:[EMAIL PROTECTED]
% >> 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
[EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
