On 02/02/2011 09:14, Shane Hathaway wrote:
> On 02/02/2011 10:57 AM, Chris Withers wrote:
>> Er, since when? If that were the case, I'm sure Shane would place
>> explicit instructions that it should not be used...
>
> Safe is relative. MySQL is a good choice for Facebook, but if I knew my
> bank wa
On 02/02/2011 10:57 AM, Chris Withers wrote:
> Er, since when? If that were the case, I'm sure Shane would place
> explicit instructions that it should not be used...
Safe is relative. MySQL is a good choice for Facebook, but if I knew my
bank was storing my account balance in MySQL, I would clo
On 01/02/2011 23:10, Ruda Porto Filgueiras wrote:
> I had similar issues on past and now I follow some rules:
>
> - pack only with zodbpack
> - pack-gc = false
...which means your database will still slowly (or quickly in my case!)
grow over time with unreferenced objects.
> - pack when th
Only to give some feedback:
I had similar issues on past and now I follow some rules:
- pack only with zodbpack
- pack-gc = false
- pack when the database is not been active update or not update at all.
But it does not imply RelStorage bug, since MySQL is know to not be so "safe".
I'm happy t
Hi Shane,
Thanks for pursuing this.
I have lots of other ideas now, but I don't know which to pursue. I need a
> lot more information. It would be helpful if you sent me your database to
> analyze. Some possible causes:
>
> - Have you looked for filesystem-level corruption yet? I asked this b
On 01/24/2011 02:02 PM, Anton Stonor wrote:
> Now, I wonder why these pointers were deleted from the current_object
> table in the first place. My money is on packing -- and it might fit
> with the fact that we recently ran a pack that removed an unusual large
> amount of transactions in a single p
On 01/24/2011 06:32 PM, Laurence Rowe wrote:
> Must this imply a failure to maintain a foreign key constraint? While
> there are FK constraints on current_object (zoid, tid) -> object_state
> (zoid, tid) there is no foreign key that might prevent a
> current_object row from being incorrectly delet
On 24 January 2011 21:28, Shane Hathaway wrote:
> On 01/24/2011 02:02 PM, Anton Stonor wrote:
>> Hi there,
>>
>> We have recently experienced a couple of PosKey errors with a Plone 4
>> site running RelStorage 1.4.1 and Mysql 5.1.
>>
>> After digging down we found that the objects that were throwi
On 01/24/2011 02:02 PM, Anton Stonor wrote:
> Hi there,
>
> We have recently experienced a couple of PosKey errors with a Plone 4
> site running RelStorage 1.4.1 and Mysql 5.1.
>
> After digging down we found that the objects that were throwing
> PosKeyErrors actually existed in the object_state t
