Re: Duplicate key issue in a transaction block

Поиск
Список
Период
Сортировка
От Vyacheslav Kalinin
Тема Re: Duplicate key issue in a transaction block
Дата
Msg-id 9b1af80e0906081004w19d463a0q9232f0be898f7947@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Duplicate key issue in a transaction block  (Bill Moran <wmoran@potentialtech.com>)
Ответы Re: Duplicate key issue in a transaction block  (Bill Moran <wmoran@potentialtech.com>)
Список pgsql-general


On Mon, Jun 8, 2009 at 8:33 PM, Bill Moran <wmoran@potentialtech.com> wrote:

Perhaps you want to take an exclusive lock on the table?  The operation
you describe seems to suggest that you'd want to guarantee exclusive
write access to the table.

Exclusive table lock is a bit excessive  IMO. Locking particular group should be good, though it is not quite straightforward to achieve. I'd use advisory locks or would lock a row in a parent group table (if such table exists, if not - it might be worth to make one) referenced by rows in question.

В списке pgsql-general по дате отправления:

Предыдущее
От: Bill Moran
Дата:
Сообщение: Re: Duplicate key issue in a transaction block
Следующее
От: Madison Kelly
Дата:
Сообщение: Adding the host name to the PgSQL shell