Re: order by slowing down a query by 80 times
От | Rajesh Kumar Mallah |
---|---|
Тема | Re: order by slowing down a query by 80 times |
Дата | |
Msg-id | AANLkTimScoXZXF9Dq797f611P6qi4MRY3SVPshDPLSpK@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: order by slowing down a query by 80 times (Yeb Havinga <yebhavinga@gmail.com>) |
Список | pgsql-performance |
On Mon, Jun 28, 2010 at 5:09 PM, Yeb Havinga <yebhavinga@gmail.com> wrote:
seq_scans is NOT explicitly disabled. The two queries just differed in the order by clause.
regds
Rajesh Kumar Mallah.
Rajesh Kumar Mallah wrote:The 63 ms query result is probably useless since it returns a limit of 25 rows from an unordered result. It is not surprising that this is fast.Dear List,
just by removing the order by co_name reduces the query time dramatically
from ~ 9 sec to 63 ms. Can anyone please help.
The pain is here:It looks like seq_scans are disabled, since the index scan has only a filter expression but not an index cond.
Index Scan using profile_master_co_name on profile_master b (cost=0.00..1125295.59 rows=6968 width=25) (actual time=0.097..9193.154 rows=2212 loops=1)
Filter: ((co_name IS NOT NULL) AND ((co_name_vec)::tsvector @@ to_tsquery('manufacturer'::text)))
seq_scans is NOT explicitly disabled. The two queries just differed in the order by clause.
regds
Rajesh Kumar Mallah.
regards,
Yeb Havinga
Regds
Rajesh Kumar Mallah.
В списке pgsql-performance по дате отправления: