Shane,
I think the pre-pack will take that long (we have never waited long enough for
a gc pack to complete the first stages). We have db replication and I'll peel
of one of the slaves to do the pack... so it's not the end of the world (unless
the db is hosed :) )
-EAD
On Jun 22, 2011, at
On 06/22/2011 04:37 PM, Shane Hathaway wrote:
> On 06/22/2011 04:27 PM, Erik Dahl wrote:
>> Ugh. Ok I'll see what we get. So I'm clear we are looking for references
>> to the object/tid pairs that don't exist. Pack will take at lest 2 days to
>> run. :(
>
> Well, just pre-pack shouldn't take t
On 06/22/2011 04:27 PM, Erik Dahl wrote:
> Ugh. Ok I'll see what we get. So I'm clear we are looking for references to
> the object/tid pairs that don't exist. Pack will take at lest 2 days to run.
> :(
Well, just pre-pack shouldn't take that long (I hope).
Shane
Ugh. Ok I'll see what we get. So I'm clear we are looking for references to
the object/tid pairs that don't exist. Pack will take at lest 2 days to run. :(
-EAD
On Jun 22, 2011, at 5:08 PM, Shane Hathaway wrote:
> On 06/21/2011 07:18 AM, Erik Dahl wrote:
>> I'm using relstorage 1.4.2 durin
On 22/06/2011 22:25, Shane Hathaway wrote:
> I think RelStorage is ready to become more of a community project, and
> part of that is changing the meaning of "supported". Until now, it has
> meant "Shane is confident that this configuration will not lose your
> data, because he has tested it repea
On 06/21/2011 08:22 AM, Philip K. Warren wrote:
> Does RelStorage work with MySQL 5.5? I saw a note posted back in
> February on this list that said that 5.5 is not yet supported, however I
> haven't seen any issues with this configuration.
>
> I have been able to successfully run the 1.4.2 and 1.5
On 06/21/2011 07:18 AM, Erik Dahl wrote:
> I'm using relstorage 1.4.2 during a batch job I was running last night I got
> the following errors.
>
> 2011-06-21 07:55:02,664 WARNING relstorage: POSKeyError on oid 23916102: no
> tid found; Current transaction is 256466219826629358; Recent object tid
