Comments on: Maatkit version 1579 released http://www.xaprb.com/blog/2007/12/27/maatkit-version-1579-released/ Stay curious! Mon, 13 May 2013 05:55:40 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Xaprb http://www.xaprb.com/blog/2007/12/27/maatkit-version-1579-released/#comment-14120 Xaprb Wed, 02 Jan 2008 21:05:35 +0000 http://www.xaprb.com/blog/2007/12/27/maatkit-version-1579-released/#comment-14120 You’re right, there’s no way to prevent the deletes.

I can think of only one possibly bad consequence of allowing this. That is with the –no-ascend option, which might get into an infinite loop. That’s easy to solve: just make –no-delete and –no-ascend mutually exclusive.

Please enter this as a feature request in the Sourceforge bug tracker. I’m going to need to get into this code pretty soon for my own purposes: to allow bulk inserts and deletes. I’ll probably go ahead and add this feature too at the same time.

]]> By: J.G. http://www.xaprb.com/blog/2007/12/27/maatkit-version-1579-released/#comment-14119 J.G. Wed, 02 Jan 2008 20:49:29 +0000 http://www.xaprb.com/blog/2007/12/27/maatkit-version-1579-released/#comment-14119 So, just out of curiosity (okay, okay, and because I need it, too) would it be possible/sensical to add some flavor of –no-delete option or the like to stop the archiver tool from deleting rows from the source table?

I have an archive server set up, and I want to have up-to-the-minute data on it, but I want that data also available on the primary server, which will delete older data periodically on its own. So the archiver tool seems to be able to do exactly what I want (I can already limit it to just new rows by using a WHERE clause), but the delete bit is problematic.

(And it doesn’t seem like you can stop it from doing the delete with just a plugin, either)

Thoughts?

]]>