pgsql: Factor out lock cleanup code that is needed in several places in

Поиск
Список
Период
Сортировка
От tgl@svr1.postgresql.org (Tom Lane)
Тема pgsql: Factor out lock cleanup code that is needed in several places in
Дата
Msg-id 20050519233018.F3B0852844@svr1.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Factor out lock cleanup code that is needed in several places in lock.c.
Also, remove the rather useless return value of LockReleaseAll.  Change
response to detection of corruption in the shared lock tables to PANIC,
since that is the only way of cleaning up fully.
Originally an idea of Heikki Linnakangas, variously hacked on by
Alvaro Herrera and Tom Lane.

Modified Files:
--------------
    pgsql/contrib/userlock:
        user_locks.c (r1.16 -> r1.17)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/userlock/user_locks.c.diff?r1=1.16&r2=1.17)
    pgsql/src/backend/storage/lmgr:
        lock.c (r1.151 -> r1.152)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lock.c.diff?r1=1.151&r2=1.152)
    pgsql/src/include/storage:
        lock.h (r1.85 -> r1.86)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lock.h.diff?r1=1.85&r2=1.86)

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: pgsql: Split the shared-memory array of PGPROC pointers out of the
Следующее
От: tgl@svr1.postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Update comment that I missed the first time around.