the lock mechanism

From: "Sumaira Ali" <nat_lazy(at)hotmail(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: the lock mechanism
Date: 2003-02-04 23:25:02
Message-ID: F1279pbKWZfEAkqBiBs00000c14@hotmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

<html><div style='background-color:'><DIV>hi,</DIV>
<DIV>&nbsp;i found this piece of documentation on user locks in the postgresql source code in the file lock.c</DIV>
<DIV>"<FONT color=#008000 size=2>
<P>User locks are handled totally on the application side as</P>
<P>* long term cooperative locks which extend beyond the normal</P>
<P>* transaction boundaries. Their purpose is to indicate to an</P>
<P>* application that someone is `working' on an item. So it is</P>
<P>* possible to put an user lock on a tuple's oid, retrieve the</P>
<P>* tuple, work on it for an hour and then update it and remove</P>
<P>* the lock. While the lock is active other clients can still</P>
<P>* read and write the tuple but they can be aware that it has</P>
<P>* been <FONT size=5><EM><U>locked at the <STRONG>application </STRONG>level </U></EM></FONT>by someone."*/</P>
<P>could some one enlighten me on the meaning of " locked at application level in this context..!!</P>
<P>thanks</P>
<P>sumaira</P>
<P>&nbsp;</P>
<P>&nbsp;</P></FONT></DIV></div><br clear=all><hr>Tired of spam? Get <a href="http://g.msn.com/8HMAENUS/2734">advanced junk mail protection</a> with MSN 8.</html>

Attachment Content-Type Size
unknown_filename text/html 1.1 KB

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Scott Morrison 2003-02-04 23:35:27
Previous Message Tom Lane 2003-02-04 23:09:46 Re: Inserting / selecting rows with TIMESTAMP