Nate wrote: > > Sorry Cami, I missed the loop. This was initially noticed by > watching the mysql process monitor and seeing LIMIT 100000 at the end > of the policyd cleanup queries. I missed entirely the loop which > exists that resends the query if 100000 rows were affected. With > that explanation it makes perfect sense. Thank you for pointing that > out. I feel a little hammered by your reply, I was only trying to > contribute and help.
I appologise for the previous mail, the tone was uncalled for. > We're running 5.0.x version of mysql, I wonder if 5.0 or 5.1 has > better delete code than previous versions which may eliminate the > issue of large deletes. I certainly hope so. I personally haven't tested MySQL 5.1 with the large deletes. Cami ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
