[EMAIL PROTECTED] wrote:
On Fri, 2003-06-20 at 15:53, Yusuf wrote:
Why would the following query take soo long to run? What does 28.12 msec represent, since the total running time is 16801.86 ms.
I'd hazard to guess that you have a whole slew of foreign keys cascading to delete, update, or check many rows from other tables.
Those are not represented in the explains at the moment.
That's what I thought at first, so I dropped the foreign key constraints. The table is referenced by 2 tables, one of which has around 200 000 records and the other has 0 records.
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
