Wietse Venema:
> Howard Chu:
> > The first patch adds a lock handler to the dict interface. I needed this
> > first, because MDB is fully transactional and does its own
> > locking/concurrency
> > management. In particular, it does MVCC so readers always run lockless;
> > since
> > they're fully isolated there's no actual need for "shared locks."
>
> That change is unnecessary. All you need is a way to tell the caller
> that it must not perform explicit lock management.
>
> You can satisfy that need that without damage to existing code,
> simply by introducing a new flag that the caller can test.
>
> I already have flags with which a map can announce its properties.
> For example, if the map can be used for security-sensitive data,
> or if it matches the lookup keys against fixed strings or against
> patterns.
>
> You're welcome to add another flag that says "I can take care of
> locks if I need to, thank you very much".
On second consideration, this may also help with memcache deployment.
I'll investigate further - changes in table infrastructure can
affect a lot of Postfix.
Wietse
