Re: [PERFORM] Wrong actual number of rows in the Query Plan

2013-02-28 Thread Tom Lane
Vahe Evoyan writes: > Merge Join (cost=0.00..2513.96 rows=1 width=72) (actual > time=127.361..473.687 rows=66460 loops=1) >Merge Cond: ((v1.dft_id = v2.dft_id) AND ((v1.key)::text = > (v2.key)::text)) >-> Index Scan using qor_value_self_join on qor_value v1 > (cost=0.00..1255.60 rows=27

[PERFORM] Wrong actual number of rows in the Query Plan

2013-02-28 Thread Vahe Evoyan
Hello, The Query Plan for the query below shows a large number in its actual rows count by an unknown reason. As a result Merge Join works on a large enough data to slow down the query. The table which I query has the following description: