[Zodb-checkins] CVS: ZODB3 - NEWS.txt:1.33.6.33

Tim Peters tim.one at comcast.net
Mon Jun 21 22:11:14 EDT 2004


Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv12383

Modified Files:
      Tag: Zope-2_7-branch
	NEWS.txt 
Log Message:
Collector 1327:  FileStorage init confused by time travel

If the system clock moved back in time more than 30 days between
a FileStorage close and (re)open, new txn ids could be smaller
than txn ids already in the database.  Plugged that hole.

Includes a stripped-down rewrite of the new test in ZODB 3.3.  Main
difference is that this version doesn't automatically check that new
log messages are actually produced; that's easier to do in 3.3,
building on an extension to the logging package Jim wrote for Zope 3.


=== ZODB3/NEWS.txt 1.33.6.32 => 1.33.6.33 ===
--- ZODB3/NEWS.txt:1.33.6.32	Fri Jun 18 10:37:42 2004
+++ ZODB3/NEWS.txt	Mon Jun 21 22:10:44 2004
@@ -1,3 +1,23 @@
+What's new in ZODB3 3.2.3 ...
+=========================
+Release date: MM-DDD-2004
+
+
+Storages
+--------
+
+Collector #1327 FileStorage init confused by time travel.
+If the system clock "went backwards" a long time between the times a
+FileStorage was closed and reopened, new transaction ids could be
+smaller than transaction ids already in the storage, violating a
+key invariant.  Now transaction ids are guaranteed to be increasing
+even when this happens.  If time appears to have run backwards at all
+when a FileStorage is opened, a new message saying so is logged at
+warning level; if time appears to have run backwards at least 30
+minutes, the message is logged at panic level (and you should
+investigate to find and repair the true cause).
+
+
 What's new in ZODB3 3.2.2
 =========================
 Release date: 18-Jun-2004




More information about the Zodb-checkins mailing list