On Wed, 3 Sep 2003, Uri Guttman wrote:
> IMO the simplest solution is a global
> mutex when doing any scans through the pmcs.
For the lock to be useful any and all mutators would have to aquire it, as
well as anyone reading the shared variables, since we need to keep anyone
from changing the in
Uri Guttman <[EMAIL PROTECTED]> wrote:
> so i don't see any major downside to a global mutex vs the nastiness of
> deadlocks and handling them. the mutex means no difficult coding issues
> and it can handle all the different (i agree with dan and vote for one
> common scan iterator) possible scan
in following the threads on traversing pmc trees, we seem to have
reached a deadlock (pun intended). deadlock detection is a pain as most
db designers have found. they don't dare to db level locking for fear of
slowdowns. dbs are always modifying rows and tables so fine grained
locking is imperati
