On Wed, 20 Jun 2001, Bruno Boettcher wrote:
> i have a lots of threads that work on a table, making insertions,
> updates removes.....
>
> now i certain cases its important to keep data integrity, so i looked
> into locks....
What kind of data integrity are you trying to implement?
> all i found was a lock function that locks the entire table....
>
> now even in shared mode, if i understand it well this means that as long
> as the locking procedure isn't finished, no other thread can update or
> delete data, right? Thats really harsh, since there are really an awful
> lot of threads....
>
> isn't it possible to lock only a specific row?
Yes. Look at SELECT ... FOR UPDATE. That should lock those rows
matched such that another transaction that attempts to select for update,
update or delete those rows waits until the locking transaction finishes.
> and what happens to other insert queries whilst the lock is operational?
> Are they postponed and the valling thread waits, or does the call return
> with an error?
IIRC, postponed until the transaction that made the lock commits or
rolls back.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
