RE: Revisited: Transactions, insert unique.
От | Peter Eisentraut |
---|---|
Тема | RE: Revisited: Transactions, insert unique. |
Дата | |
Msg-id | Pine.GSO.4.02A.10004270944221.23225-100000@Duva.DoCS.UU.SE обсуждение исходный текст |
Ответ на | RE: Revisited: Transactions, insert unique. ("Hiroshi Inoue" <Inoue@tpf.co.jp>) |
Ответы |
RE: Revisited: Transactions, insert unique.
|
Список | pgsql-general |
On Thu, 27 Apr 2000, Hiroshi Inoue wrote: > PostgreSQL's SERIALIZABLE isolation level would allow both inserts. > READ COMMITED isolation level wouldn't allow A's inserts. > > As I mentioned in another posting,PostgreSQL's SERIALIZABLE > isolation level isn't completely serializable and it's same as Oracle. > Probably Vadim refers to this incomplete serializability somewhere > in documentation. > It seems almost impossible to implement complete serializability > under MVCC without using table level locking. I love MVCC much > more than theoretically beautiful complete serializability. Given that Postgres correctly recognizes concurrent updates and aborts one of the transactions, how difficult would it be to do the same for inserts? -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
В списке pgsql-general по дате отправления: