Paul J Stevens wrote: > Jon, > > there's no need to update the header cache. >
Ok, I wasn't sure. I didn't think it needed to be done. Throttling the movement would be difficult. While the processing could be done on another box separate of the production daemons, the database load and disk bottleneck is the real key. On MySQL, an INSERT LOW_PRIORITY could be used. This would effectively let the database do the throttling by making the migration process wait for the insert to be completed when the table goes idle. And when dropping the rows from the messageblks, a DELETE LOW_PRIORITY can also be used to keep from deleting the old rows until the table is idle. Does Postgres have a similar option for insert and/or delete? I doubt that we need to worry about SQLite for an option as it doesn't have a daemon running to order query execution. -Jon -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
