Re: Locking entire database

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Panagiotis Pediaditis" <pped(at)ics(dot)forth(dot)gr>
Cc: "Thomas Kellerer" <spam_eater(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Locking entire database
Date: 2007-09-14 16:21:19
Message-ID: dcc563d10709140921y7a9e1f84y72a471aa92effa86@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 9/14/07, Panagiotis Pediaditis <pped(at)ics(dot)forth(dot)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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alan Hodgson 2007-09-14 16:21:51 Re: Inherited FK Indexing
Previous Message Scott Marlowe 2007-09-14 16:20:19 Re: Inherited FK Indexing