From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-committers(at)postgresql(dot)org> |
Subject: | RE: pgsql/src/backend/storage/lmgr (lmgr.c lock.c proc.c README) |
Date: | 2001-01-12 23:59:41 |
Message-ID: | EKEJJICOHDIEMGPNIFIJIELGDEAA.Inoue@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
> -----Original Message-----
> From: tgl(at)postgresql(dot)org
> Sent: Friday, December 22, 2000 9:52 AM
> To: pgsql-committers(at)postgresql(dot)org
> Subject: [COMMITTERS] pgsql/src/backend/storage/lmgr (lmgr.c lock.c
> proc.c README)
>
> ----------------------------- Log Message -----------------------------
>
> Revise lock manager to support "session level" locks as well as
> "transaction
> level" locks.
[snip]
> I also took this opportunity to do some cleanup and renaming in the lock
> code. The previously noted bug in ProcLockWakeup, that it
> couldn't wake up
> any waiters beyond the first non-wakeable waiter, is now fixed.
I've just noticed that this changed a locking behabior.
For example, VACUUM could hardly acquire the lock
while other backends frequently access the target table.
Regards.
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-13 00:26:49 | Re: pgsql/src/backend/storage/lmgr (lmgr.c lock.c proc.c README) |
Previous Message | petere | 2001-01-12 22:36:58 | pgsql/contrib/intarray (Makefile.703) |