Follow

@dave Then you can decouple the task of physically removing the records, have a sweeper during slow times which nukes things where the lastseen timeval is older than the lastscanned timeval of the feed itself.

2/2

· · Web · 1 · 0 · 0

@vandys I like the idea of a cron job to clean that up on a timer.

How much of a performance hit is it when you try to INSERT and there is an index collision. Is it basically like a NOOP, or is there still some overhead with that? Just not sure how much of a big deal it is to have all those inserts still colliding after I remove the ON DUPLICATE KEY UPDATE purge=0 clause.

Sign in to participate in the conversation
PodcastIndex Social

Intended for all stake holders of podcasting who are interested in improving the eco system