On 9/18/06, Josh Berkus <josh@agliodbs.com> wrote:
All,
Is UserLocks a cool enough feature to be worth mentioning in the 8.2 PR?
If so, can someone explain it to me off-list? I still don't get what it
does ...
yes, i can explain it in detail, and am willing to kick in some
documentation. it is very cool, and relatively undiscovered. email
me for details.
the short answer is you can do long term locking (not scoped to
transaction) using the postgresql high speed internal lock engine.
this allows you to bypass various locking hacks such as keeping
transactions (too) long term, or maintaining a lock flag in a table,
which has cleanup issues.
they are great if you need to emulate pessimistic locking and
transactions is an awkward fit. its up to you, the user to determine
when and what to lock.
i really beat on the user (advisory locks) when doing a cobol/isam
conversion project. they work fabulous.
merlin
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
