Re: Some more concurrency fun
Re: Some more concurrency fun
- Subject: Re: Some more concurrency fun
- From: Miguel Arroz <email@hidden>
- Date: Mon, 28 Jan 2008 23:46:16 +0000
Hi!
Instance 1 > teste=# begin;
Instance 1 > BEGIN
Instance 2 > teste=# begin;
Instance 2 > BEGIN
Instance 1 > teste=# update test set some_value = 200 where test_id =
1 and some_value = 100;
Instance 1 > UPDATE 1
Instance 2 > teste=# update test set some_value = 300 where test_id =
1 and some_value = 100;
(pause, instance 2 blocked)
Instance 1 > teste=# commit;
Instance 1 > COMMIT
(instance 2 is back)
Instance 2 > UPDATE 0
Bum! It works! :)
I did it directly on the psql command line, the results should be
the same. Ufff...
I haven't noticed that thing about transaction hanging in the
manual, but it sure works. :) No need for serializing.
Thanks for the help guys!
Yours
Miguel Arroz
On 2008/01/28, at 21:54, Mike Schrag wrote:
The second paragraph is the key.
Incidentally, it should be really easy to verify this behavior if
you're still concerned by writing two main methods that just call
JDBC directly with "wait for key presses" at each stage of the
transaction. Run both concurrently and just move them through each
stage of the transaction manually.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40guiamac.com
This email sent to email@hidden
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden