Eugene [EMAIL PROTECTED] writes:
Can I force HashAggregation before index scan?
No. But look into why the planner's rows estimate is so bad here:
- Index Scan using refseq_sequence_key2 on refseq_sequence s
(cost=0.00..1516.06 rows=389
width=24) (actual time=0.352..491.107 rows=27391
I have a very simple problem. I run two select statments, they are identical except
for a single
where condition. The first select statment runs in 9 ms, while the second statment
runs for 4000
ms
SQL1 - fast 9ms
explain analyse select seq_ac from refseq_sequence S where seq_ac in (select
