| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Lincoln Yeoh'" <lyeoh(at)pop(dot)jaring(dot)my>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: Lock on arbitrary string feature |
| Date: | 2001-01-11 17:20:19 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D3259@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-01-11 17:25:16 | Re: drop table and pg_proc |
| Previous Message | Corrado Giacomini | 2001-01-11 17:18:45 | conflicting types for `struct Oid' |