--- Alvaro Herrera <[EMAIL PROTECTED]> wrote: > On Thu, Nov 27, 2003 at 12:40:28AM +0100, Andreas Pflug wrote: > > > A common mistake, can't count how often I created this one... And not > > easy to find, because EXPLAIN won't explain triggers. > > That's a pity. And the lack of EXPLAINing function execution, too. > Maybe it's not that hard to do? >
I'd like to emphasize again that NOT having an index on the FK column is a perfectly valid approach, despite some opinions to the contrary. In fact, requiring an index on FK column(s) when it is not required by the application's logic IS a mistake since it slows down inserts/deletes/updates/vacume/reindex/etc on the respective table and wastes disk space (could be considerable amount on large tables). Also, FK column index DOES NOT, in general, solve performance issues with FK verification check. Someone may (and, I'm sure, will) simply have more data or more constraints. The only solution here appears to be the "--disable-triggers" option as it was suggested by Robert Treat. If it works then I'm fine, somehow I did not see that option in the beginning. Thanks __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ---------------------------(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
