[EMAIL PROTECTED] wrote: > > He found some MySQL document stating that with MyISAM tables, the complete > table gets locked during database operations, > whereas InnoDB type of table would only lock the particular table row (but be > somewhat slower in use).
Correct. > Could there be some problem, with regards to DB or table locking and policyd > accessing the tables at same time? Well, when LOCK's occur, queries from Policyd -> MySQL will (forcefully) timeout to prevent any delay. The reason we are using MyISAM instead of InnoDB is because during testing under really high loads, we found that InnoDB would not only be slower, but it would actually crash. Perhaps InnoDB needs to be re-evaluated with the latest release. Are you able to switch your Policyd database over to InnoDB? (this will require some work, including a few Policyd changes) Cami ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
