Re: Transaction in plpgslq - Mailing list pgsql-sql

From Andrew Hammond
Subject Re: Transaction in plpgslq
Date
Msg-id 4293520E.30005@ca.afilias.info
Whole thread Raw
In response to Re: Transaction in plpgslq  (Rafa Couto <rafacouto@gmail.com>)
List pgsql-sql
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rafa Couto wrote:
> I understand "FOR UPDATE" clause is locking while is selecting rows
> only. It does not secure atomic execution from 'SELECT' to 'UPDATE' in
> next statement. Is not it?

Locks adhere until the transaction ends. I included links to relevant
documentation in my original post. If you read up on locking, you'll
find the answer to your problem. Please post any further questions you
have after reading the documentation.

- --
Andrew Hammond    416-673-4138    ahammond@ca.afilias.info
Database Administrator, Afilias Canada Corp.
CB83 2838 4B67 D40F D086 3568 81FC E7E5 27AF 4A9A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCk1INgfzn5SevSpoRAjVlAJ4kGMlTQFaI1BW+9O9GT8He19TyLACcCYtU
Tucg2FuGiDggsAwV7JA2HHs=
=9rus
-----END PGP SIGNATURE-----


pgsql-sql by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Transaction in plpgslq
Next
From: CG
Date:
Subject: DROP IF ...