RS> I have two other minor worries about this technique. First, it would
RS> seem possible that if, say, we have slot1 in object1 which was set to
RS> :some-opt at some time in the past, but is now totally unused by any
RS> object, the blob row containing that would be considered dead; if
RS>
On Thu, Dec 11, 2008 at 6:09 PM, Robert Synnott wrote:
> I have two other minor worries about this technique. First, it would
> seem possible that if, say, we have slot1 in object1 which was set to
> :some-opt at some time in the past, but is now totally unused by any
> object, the blob row conta
2008/12/11 Henrik Hjelte :
> I agree with Alex, just one perhaps obvious comment: I would have one
> transaction around cleaning up one blob-id, not a big transaction
> around cleaning up the whole blob table. If you do several
> transactions it doesn't lock up much, so it
> should be able to execu
HH> I agree with Alex, just one perhaps obvious comment: I would have one
HH> transaction around cleaning up one blob-id, not a big transaction
HH> around cleaning up the whole blob table. If you do several
HH> transactions it doesn't lock up much, so it
HH> should be able to execute at the sa
I agree with Alex, just one perhaps obvious comment: I would have one
transaction around cleaning up one blob-id, not a big transaction
around cleaning up the whole blob table. If you do several
transactions it doesn't lock up much, so it
should be able to execute at the same time as a database is
RS> then the slot definitions in the slot table are removed, but the
RS> actual slot _values_, which live in the blob table, are retained. Is
RS> this intended behaviour?
yep, it is. it sort of sucks, i know.
whether or not it becomes a problem depends on what kind of data
you store in slots.
2008/12/10 Ian Eslick <[EMAIL PROTECTED]>:
> Have you updated from elephant-unstable recently? I found a bug where
> indices were not properly updated that I think was in the core
> elephant code. However there may be a bug specific to postmodern.
>
> Ian
>
Nope, this isn't the problem, or at le
Have you updated from elephant-unstable recently? I found a bug where
indices were not properly updated that I think was in the core
elephant code. However there may be a bug specific to postmodern.
Ian
On Dec 10, 2008, at 3:38 PM, Robert Synnott wrote:
> Hi,
> From my experimenting, it se
