Hi, thanks for the reply! I've tried wrapping my get-instances, that's fine and will work for now. I've tried ugrading elephant - that did not work at all - unable to open the db at all - but I don't have the details here, I'll try a bit harder, and if I get stuck I might post separately about this. Rebuilding indices sounds interesting - I'll investigate in how to do this!
Thanks , Aslak On Thu, Apr 23, 2009 at 5:36 PM, Leslie P. Polzer <s...@viridian-project.de>wrote: > > > I've been using elephant 0.91 for quite a while now, with a berkeley 4.6 > > backend, and it's been a joy. > > Great! :) > > > > Recently however, as usage has gone up, some problems have started > occuring. > > One big problem has been that when I run (get-instances-by-class 'foo) I > get > > a list of foo, but with some nil's occuring as well. > > Is this a sign of database corruption? > > Not necessarily, I'd rather guess at a bug in the indexing mechanism > that has been solved by now. > > > > How do I remedy this? > > Some possible solutions: > > * upgrade your Elephant > > * rebuild your indices > > * wrap your get-instances stuff in a function that removes > the NIL entries > > > > I've tried running both the recover and checkpoint tools on the db, but > > no change. > > No, that won't help. :) > > > > I've experienced deadlocks as well, and had to kill my sbcl > > FYI you can prevent deadlocks from appearing. > > > > - wondering if that (non clean shutdown) is what caused the problems > > in the first place. > > I don't think so. > > > > Or is this something to do with indexes - could they be remade somehow? > > I think there was an easy way but I can't remember it right now... > > Cheers, > > Leslie > > -- > LinkedIn Profile: http://www.linkedin.com/in/polzer > Xing Profile: https://www.xing.com/profile/LeslieP_Polzer > Blog: http://blog.viridian-project.de/ > > -- Mvh Aslak
_______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
