I can't reproduce the above. Are you sure T2 isn't committing?
Arch, damn, yes, bugger...
If it were, since the default isolation level is read committed,
Ok, that explains it.
But my second question is still unanswered: Is the key value locking, that
is implemented in postgres, ARIES/KVL?
Does Postgres garantee repeatable-read (RR) during transactions? And does it
implement ARIES/KVL?
If so, why is the following possible?
T1: begin;
T1: select * from table;
(notice the row with id = X)
T2: begin;
T2: delete from table where id = X;
T1: select * from table;
(notice the row
We have been there, done that, and decided it was a bad idea. I suggest
you do a little reading in the mail list archives.
I have searched the lists archives for the words commit, autocommit and
transaction but couldn't find any discussion on wheter to give a database
administrator the option
I'm not sure that this is the right list to ask - but after having googled a
while it seems that the only ones that might be able to answer this question
is the developers. Therefor, here we go:
As far as I have understood, postgres is autocommiting each typed statement
UNLESS the user
