Re: Locking entire database
От | Panagiwths Pediadiths |
---|---|
Тема | Re: Locking entire database |
Дата | |
Msg-id | Pine.GSO.4.58.0709151127160.22751@calliope обсуждение исходный текст |
Ответ на | Re: Locking entire database ("Scott Marlowe" <scott.marlowe@gmail.com>) |
Ответы |
Re: Locking entire database
Re: Locking entire database |
Список | pgsql-general |
Thats the fun part, I actually need to allow duplicates in specific cases but not in this one :) Shouldn't the serializable level prevent these duplicates? As I understand it serializable should give the same result as if the transactions were performed the one after the other. Thnx Panagiotis On Fri, 14 Sep 2007, Scott Marlowe wrote: > On 9/14/07, Panagiotis Pediaditis <pped@ics.forth.gr> wrote: > > A simpler example, > > In the context of one transaction i do many queries of the form > > INSERT INTO table value WHERE value NOT IN TABLE; > > > > If i have 2 processes running the same 100s of these at the same time i > > end up with duplicates. > > Even with isolation set to serializable > > any ideas? > > Unique index? >
В списке pgsql-general по дате отправления: