RE: Lock on arbitrary string feature
| От | Mikheev, Vadim | 
|---|---|
| Тема | RE: Lock on arbitrary string feature | 
| Дата | |
| Msg-id | 8F4C99C66D04D4118F580090272A7A234D3259@sectorbase1.sectorbase.com обсуждение исходный текст | 
| Ответ на | Lock on arbitrary string feature (Lincoln Yeoh <lyeoh@pop.jaring.my>) | 
| Ответы | RE: Lock on arbitrary string feature | 
| Список | pgsql-hackers | 
> In contrast the current alternatives appear to be either LOCK > the entire table (preventing ALL inserts and selects), SHARE ROW EXCLUSIVE mode doesn't prevent selects... > or to create a UNIQUE constraint (forcing complete rollbacks > and restarts in event of a collision :( ). Hopefully, savepoints will be in 7.2 > Any comments, suggestions or tips would be welcome. It looks > like quite a complex thing to do - I've only just started > looking at the postgresql internals and the lock manager. It's very easy to do (from my PoV -:)) We need in yet another pseudo table like one we use in XactLockTableInsert/XactLockTableWait - try to look there... Vadim
В списке pgsql-hackers по дате отправления: