Re: Implicit Lock Row - Mailing list pgsql-hackers

From Shridhar Daithankar
Subject Re: Implicit Lock Row
Date
Msg-id 3DA1DD70.26665.106230D4@localhost
Whole thread Raw
In response to Implicit Lock Row  ("Antoine Lobato" <Antoine.Lobato@wanadoo.fr>)
List 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

ByeShridhar

--
Strategy:    A long-range plan whose merit cannot be evaluated until sometime    
after those creating it have left the organization.



pgsql-hackers by date:

Previous
From: "Shridhar Daithankar"
Date:
Subject: Table spaces again [was Re: Threaded Sorting]
Next
From: Hans-Jürgen Schönig
Date:
Subject: Re: Table spaces again [was Re: Threaded Sorting]