On MySQL 5.5, if I perform a DELETE LOW_PRIORITY query, are the deleted rows visible in future SELECT statements while the query is waiting for all reads to stop, or are they made invisible to clients making SELECTS on the same table?
@ObsessiveFOSS I can't answer from experience, but it seems to be the point of LOW_PRIORITY that the rows are visible until no-one is reading them any more and the delete kicks in
I have a large MyISAM table on MySQL 5.5(Windows XP x64) on which I will have to run DELETE LOW_PRIORITY queries. Does DELETE LOW_PRIORITY make the rows invisible to SELECT statements immediately and actually delete the rows from disk when no clients are accessing the table, or is the point delay...
@DTest I, for some odd reason, can't get MySQL5.6 to even start cleanly, even after a typical installation. I have gone as far as reinstalling Windows. I guess I'll have to wait for a stable version. 5.5 works really well, though.
@ObsessiveFOSS InnoDB is row-level locking, no config needed. You can configure it to get 'dirty reads' (ie, be able to read rows that are locked to be deleted before the delete has finished).