Re: [PERFORM] Seqscan problem

Tom Lane writes: Vlad Arkhipov <[EMAIL PROTECTED]> writes: I've just discovered a problem with quite simple query. It's really confusing me. Postgresql 8.3.1, random_page_cost=1.1. All tables were analyzed before query. What have you got effective_cache_size set to?

Re: [PERFORM] Seqscan problem

Vlad Arkhipov <[EMAIL PROTECTED]> writes: > I've just discovered a problem with quite simple query. It's really > confusing me. > Postgresql 8.3.1, random_page_cost=1.1. All tables were analyzed before > query. What have you got effective_cache_size set to? regards, tom

[PERFORM] Seqscan problem

I've just discovered a problem with quite simple query. It's really confusing me. Postgresql 8.3.1, random_page_cost=1.1. All tables were analyzed before query. EXPLAIN ANALYZE SELECT i.c, d.r FROM i JOIN d ON d.cr = i.c WHERE i.dd between '2007-08-01' and '2007-08-30' Hash Join (cost=2505.4