From: Andrew Hammond <ahammond@ca.afilias.info>
To: Rafa Couto <rafacouto@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Transaction in plpgslq
Date: Tue, 24 May 2005 12:10:54 -0400
Message-ID: <4293520E.30005@ca.afilias.info> (raw)
In-Reply-To: <22df564b050524034045f8c174@mail.gmail.com>
References: <22df564b05052003479481da1@mail.gmail.com>
<428E245B.4050204@ca.afilias.info>
<22df564b050524034045f8c174@mail.gmail.com>
-----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-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ahammond@ca.afilias.info, rafacouto@gmail.com
Subject: Re: Transaction in plpgslq
In-Reply-To: <4293520E.30005@ca.afilias.info>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox