Horton

Re: Revisited: Transactions, insert unique.

Ed Loehr <eloehr@austin.rr.com>

View thread View on postgr.es
From: Ed Loehr <eloehr@austin.rr.com>
To: Rex McMaster <rmcm@compsoft.com.au>
Cc: Joachim Achtzehnter <joachim@kraut.bc.ca>, pgsql-general@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2000-04-26T22:52:44Z
Lists: pgsql-general 
rmcm@compsoft.com.au wrote:
> 
> Doesn't
> 
>      SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
> 
> have to come within transaction - ie
> 
>      BEGIN;
>      SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
> 
> In this order your test seems to behave correctly - only 1 row inserted.

Yes, my initial ordering was in error.  But even after reordering, the
point is not that only 1 row was inserted, but rather that Transaction A
was able to see the effects of transaction B when it clearly should not.

Regards,
Ed Loehr