Thanks to visit codestin.com
Credit goes to postgrespro.com

Re: Reducing relation locking overhead - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Reducing relation locking overhead
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: Reducing relation locking overhead  (Kevin Brown <[email protected]>)
Responses Re: Reducing relation locking overhead
List pgsql-hackers
Kevin Brown <[email protected]> writes:
> - when requesting a type of lock, one must first acquire all lesser
>   lock types against the object in order of strength.  Hence, one must
>   acquire AccessShareLock before acquiring AccessExclusiveLock.

This is exactly wrong ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: MIN() performance regression 8.0 -> 8.1
Next
From: Tom Lane
Date:
Subject: Re: generalizing the planner knobs