"Andy" <[EMAIL PROTECTED]> writes: > EXPLAIN ANALYZE > DELETE FROM report WHERE id_order IN > ...
> Hash IN Join (cost=3532.83..8182.33 rows=32042 width=6) (actual > time=923.456..2457.323 rows=59557 loops=1) > ... > Total runtime: 456718.658 ms So the runtime is all in the delete triggers. The usual conclusion from this is that there is a foreign key column pointing at this table that does not have an index, or is not the same datatype as the column it references. Either condition will force a fairly inefficient way of handling the FK deletion check. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match