From: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Subject: | Re: transaction confusion |
Date: | 2006-09-18 11:57:05 |
Message-ID: | 450E8991.8040209@compulab.co.il |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> I wonder if you set the transaction mode to "serializable" whether that
> would make a difference. In standard read-committed the way it works
> below seems to be what's expected (each transaction sees what was
> committed at the time is ran).
>
I tried running this in both windows at the same time (this is the inserttest() without the update
statment at the beginning):
begin;
set transaction ISOLATION LEVEL SERIALIZABLE;
select inserttest();
commit;
and I got this error:
ERROR: could not serialize access due to concurrent update
SQL state: 40001
Context: SQL statement "delete from testserial"
PL/pgSQL function "inserttest" line 2 at SQL statement
From | Date | Subject | |
---|---|---|---|
Next Message | Shane Ambler | 2006-09-18 11:59:53 | Re: Need special sequence generator |
Previous Message | A. Kretschmer | 2006-09-18 10:58:16 | Re: Need special sequence generator |