[ZODB-Dev] More ZODB POSKeyErrors with 2.6.0

[Guido van Rossum]

> > Could the index file have been for a different version of the
> > database???  E.g. what would happen if the database is updated for a
> > while, and then the storage server is killed with SIGKILL so the index
> > is not rewritten?  On storage server restart, an old version of the
> > index will be found and used, right?  Could that scenario cause this
> > effect?
> 
> Would this be happening a lot more often if this was the case?

Who knows.  One of the FileStorage developers should comment on this.

> > but not followed by a traceback?  We've seen this a few times at a
> > customer site.  
> 
> Ah good, it's not just me then :-)
> 
> What's the fix?

See my recent checkins to the zLOG package on the trunk.

--Guido van Rossum (home page: http://www.python.org/~guido/)