From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Implicit Lock Row |
Date: | 2002-10-07 13:46:00 |
Message-ID: | 3DA1DD70.26665.106230D4@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5 Oct 2002 at 23:56, Antoine Lobato wrote:
>
> I currently develop an interface to simulate a indexed sequential file
> management with PostgreSql. I must reproduce the same philosophy used of
> control of locking of the records.
> I seek a solution to lock and unlock implicitly a row of a table. The locking
> of several rows, of the same table or various tables, can last a long time and
> consequently locking cannot be included in a transaction for not to lock the
> whole table for the other users.
> There is a viable solution with PostgreSql?
> There is an accessible basic structure of locking?
You can use select for update to lock rows.
HTH
Bye
Shridhar
--
Strategy: A long-range plan whose merit cannot be evaluated until sometime
after those creating it have left the organization.
From | Date | Subject | |
---|---|---|---|
Next Message | Hans-Jürgen Schönig | 2002-10-07 13:52:54 | Re: Table spaces again [was Re: Threaded Sorting] |
Previous Message | Shridhar Daithankar | 2002-10-07 13:25:38 | Table spaces again [was Re: Threaded Sorting] |