[GENERAL] indexing - creates problem

I am having a table with more than 1000 records, i am not having index in that, while executing that query it occupies the processor.. I created an index, and then executed that query., Now it is not getting executed at all... while seeing the top the processor is busy in WA, that it is waiting

Re: [GENERAL] indexing - creates problem

I am having a table with more than 1000 records, i am not having index in that, while executing that query it occupies the processor.. 1000 rows is not much - I guess the index is not necessary at all, as the traditional sequential scan is faster than index scan (due to random access vs.

Re: [GENERAL] indexing - creates problem

now it is for 500 records. postgres 7.4 Debian -- call_id | integer | not null default nextval('call_log_seq'::text) agent_id | integer | call_id already has index.