"Mitch Vincent" <[EMAIL PROTECTED]> writes:
> EXPLAIN on a delete isn't very interesting..
> databasename=# explain delete from applicants_resumes where app_id=62908;
> NOTICE: QUERY PLAN:
> Index Scan using app_resume_app_id_index on applicants_resumes
> (cost=0.00..3.70 rows=1 width=6)
I beli
Check this out..
>
> databasename=# explain delete from resumes_fti where id=86370016;
> NOTICE: QUERY PLAN:
>
> Seq Scan on resumes_fti (cost=0.00..394577.18 rows=1956 width=6)
>
> EXPLAIN
>
> Ouch :-)
Bingo. Is there an index on id?
--
Bruce Momjian| http://w
EXPLAIN on a delete isn't very interesting..
databasename=# explain delete from applicants_resumes where app_id=62908;
NOTICE: QUERY PLAN:
Index Scan using app_resume_app_id_index on applicants_resumes
(cost=0.00..3.70 rows=1 width=6)
EXPLAIN
I'm not thinking that is what's taking so long tho
I would check with EXPLAIN to see when indexes are being used.
[ Charset ISO-8859-1 unsupported, converting... ]
> I hadn't concentrated on the INSERT/UPDATE/DELETE speed of this until today
> and I find that it's amazingly slow. Of course the time it takes is relative
> to the size of the text
I hadn't concentrated on the INSERT/UPDATE/DELETE speed of this until today
and I find that it's amazingly slow. Of course the time it takes is relative
to the size of the text but still, almost a minute to delete one record on a
Dual celeron 600 with 256 Megs of RAM and an ATA/66 7200 RPM 30 GIG
