Batch processing of huge tables

[fu]

So, I just committed a code merge for an issue we found via LJ, where comment properties weren't being deleted when the comment was.

That takes care of new properties, but we still have old ones hanging around! How do we handle this? I'm assuming that due to the size of talkprop2, doing:

delete talkprop2 from talkprop2, talk2 where talkprop2.journalid=talk2.journalid AND talkprop2.jtalkid=talk2.jtalkid AND talk2.state="D";

would be a horrible idea, but what can we do to make it less horrible? Should we even try to delete?

Comments

[foxfirefey]

Hrm....maybe there could be a worker that gets batches by the primary indexed key where talk2.state="D" and checks each one. Just slow and steady and low-key?

[zorkian]

IMO not really worth worrying about. We aren't hurting for those megabytes.