[ZODB-Dev] fixing far-future timestamps (patch)

2009-06-04 Thread Ross J. Reedstrom
Hi all - I'm one of the unfortunates who managed to break a Data.fs when migrating a ZEO backend to new hardware. Unfortunately, I missed the 'CRITICAL' error logged by ZOE (aside: is there a fail_on_critical option somewhere?) and ended up with transaction ids that parse as timestamps in the year

Re: [ZODB-Dev] fixing far-future timestamps (patch)

2009-06-09 Thread Ross J. Reedstrom
-375, Houston, TX 77005 GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E F888 D3AE 810E 88F0 BEDE On Thu, Jun 04, 2009 at 01:13:04PM -0400, Jim Fulton wrote: On Jun 4, 2009, at 12:04 PM, Ross J. Reedstrom wrote: I've successfully used this in a small python script to correct my problem

Re: [ZODB-Dev] fixing far-future timestamps (patch)

2009-06-10 Thread Ross J. Reedstrom
On Tue, Jun 09, 2009 at 06:29:38PM -0400, Jim Fulton wrote: On Jun 9, 2009, at 4:19 PM, Ross J. Reedstrom wrote: Hmm, I seem to not be receiving email from this list, even though I signed up. Anyway, saw this via the archives. Would a doctest in FileStorage be o.k.? Yup

Re: [ZODB-Dev] ZEO and relstporage performance

2009-10-14 Thread Ross J. Reedstrom
On Tue, Oct 13, 2009 at 06:30:31PM -0600, Shane Hathaway wrote: Laurence Rowe wrote: Shane's earlier benchmarks show MySQL to be the fastest RelStorage backend: http://shane.willowrise.com/archives/relstorage-10-and-measurements/ Yep, despite my efforts to put PostgreSQL on top. :-) It

Re: [ZODB-Dev] ZEO and relstporage performance

2009-10-14 Thread Ross J. Reedstrom
On Wed, Oct 14, 2009 at 02:20:50PM -0400, Benji York wrote: On Wed, Oct 14, 2009 at 1:08 PM, Ross J. Reedstrom reeds...@rice.edu wrote: shared caches: this is the main reason I've been looking at relstore: we're running many Zope FEs against one ZOE right now, and due to the nature