Re: Basic locking question - Mailing list pgsql-general

From Ben
Subject Re: Basic locking question
Date
Msg-id 431E2572.9030004@silentmedia.com
Whole thread Raw
In response to Re: Basic locking question  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Basic locking question
List pgsql-general
Right, I understand the badness of the situation, but unfortunately the
keys are externally generated and I have no control over them.

So I'm looking for "lock <tablename> in exclusive mode"?

Tom Lane wrote:

>Pretty much the only thing you can do about that is to take an exclusive
>table-level lock.  This is simple but pretty awful for concurrency
>(since the lock blocks everyone else from inserting ANY key, not only
>the one you are inserting).
>
>Consider using a sequence object to generate the keys, instead.
>
>            regards, tom lane
>
>


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Basic locking question
Next
From: Scott Marlowe
Date:
Subject: Re: SLOOOOOOOW