Hello,
After investigating FileStorage a bit, I found that GC runs on objects,
but pack later by transactions. That means that if there's a bigger-ish
transaction, we can't get rid of it until all of it's objects are GCed
(or superseeded by newer states).
Is that correct? I think yes, so an
On Thu, Mar 31, 2011 at 6:46 AM, Adam GROSZER agros...@gmail.com wrote:
Hello,
After investigating FileStorage a bit, I found that GC runs on objects,
but pack later by transactions. That means that if there's a bigger-ish
transaction, we can't get rid of it until all of it's objects are GCed
Hi.
On Thu, Mar 31, 2011 at 12:46 PM, Adam GROSZER agros...@gmail.com wrote:
After investigating FileStorage a bit, I found that GC runs on objects,
but pack later by transactions. That means that if there's a bigger-ish
transaction, we can't get rid of it until all of it's objects are GCed
On 03/31/2011 04:46 AM, Adam GROSZER wrote:
After investigating FileStorage a bit, I found that GC runs on objects,
but pack later by transactions. That means that if there's a bigger-ish
transaction, we can't get rid of it until all of it's objects are GCed
(or superseeded by newer states).
Hello,
On Thu, 31 Mar 2011 06:33:30 -0600 you wrote:
On 03/31/2011 05:25 AM, Hanno Schlichting wrote:
Hi.
On Thu, Mar 31, 2011 at 12:46 PM, Adam GROSZERagros...@gmail.com wrote:
After investigating FileStorage a bit, I found that GC runs on objects,
but pack later by transactions. That
