• T
    Simplify lock manager data structures by making a clear separation between · c599a247
    Tom Lane 提交于
    the data defining the semantics of a lock method (ie, conflict resolution
    table and ancillary data, which is all constant) and the hash tables
    storing the current state.  The only thing we give up by this is the
    ability to use separate hashtables for different lock methods, but there
    is no need for that anyway.  Put some extra fields into the LockMethod
    definition structs to clean up some other uglinesses, like hard-wired
    tests for DEFAULT_LOCKMETHOD and USER_LOCKMETHOD.  This commit doesn't
    do anything about the performance issues we were discussing, but it clears
    away some of the underbrush that's in the way of fixing that.
    c599a247
lock.h 15.6 KB