Comment 2 for bug 143481

Uploaded: BaseStorage_reset_tids.patch

I had the problem, too. The clock was set to the year 2009 for very short, but now all new tids are from 2009.

Tim Peter suggested, that you can solve the problem by doing
a storage.copyTransactionsFrom by setting the tid to None.
See bottom of:
http://mail.zope.org/pipermail/zodb-dev/2005-September/009225.html

This is a small path to BaseStorage with gives the method copyTransactionsFrom a new keyword argument "reset_tids".

If you use the method once, all tids are reset to the current time.
This means, you don't need the patch zodb-pack-future.patch anymore. I prefere this, because you only need to repair the database once, while other patch need to installed for ever.