From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Use the standard lock manager to establish priority order when |
Date: | 2005-04-30 19:03:33 |
Message-ID: | 20050430190333.8AC7E5331C@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Use the standard lock manager to establish priority order when there
is contention for a tuple-level lock. This solves the problem of a
would-be exclusive locker being starved out by an indefinite succession
of share-lockers. Per recent discussion with Alvaro.
Modified Files:
--------------
pgsql/src/backend/access/heap:
heapam.c (r1.188 -> r1.189)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/heapam.c.diff?r1=1.188&r2=1.189)
pgsql/src/backend/storage/lmgr:
lmgr.c (r1.72 -> r1.73)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lmgr.c.diff?r1=1.72&r2=1.73)
pgsql/src/include/storage:
lmgr.h (r1.47 -> r1.48)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lmgr.h.diff?r1=1.47&r2=1.48)
From | Date | Subject | |
---|---|---|---|
Next Message | James William Pye | 2005-04-30 19:20:23 | python - be: Move the XD(transaction dict) feature to the PL. |
Previous Message | User Cmaj | 2005-04-30 16:47:40 | pgaccess - pgaccess: apply modified patch for pga_tables creation bug in |