bizgres - bizgres: Add primitive deadlock detection code. - Mailing list pgsql-committers

From markir@pgfoundry.org (User Markir)
Subject bizgres - bizgres: Add primitive deadlock detection code.
Date
Msg-id 20060828041937.E08BE86C60B@pgfoundry.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Add primitive deadlock detection code. This is achieved by calling the standard
deadlock detector and treating resource locks like exclusive standard locks. The
downside is overly aggressive detection - however safety is the initial goal.

The resource lock and proclock hash tables are now merged with the standard lock
ones - and we now use the standard lock lwlock too. The reason being to ensure
safe interlocking for deadlock detection between standard and resource locks.
(see the deadlock code README for more details).

Modified Files:
--------------
    bizgres/postgresql/src/backend/storage/ipc:
        ipci.c (r1.2 -> r1.3)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/storage/ipc/ipci.c.diff?r1=1.2&r2=1.3)
    bizgres/postgresql/src/backend/storage/lmgr:
        deadlock.c (r1.1.1.2.2.1 -> r1.2)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/storage/lmgr/deadlock.c.diff?r1=1.1.1.2.2.1&r2=1.2)
        lock.c (r1.2 -> r1.3)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/storage/lmgr/lock.c.diff?r1=1.2&r2=1.3)
        proc.c (r1.1.1.2.2.1 -> r1.2)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/storage/lmgr/proc.c.diff?r1=1.1.1.2.2.1&r2=1.2)
    bizgres/postgresql/src/backend/utils/resscheduler:
        README (r1.2 -> r1.3)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/resscheduler/README.diff?r1=1.2&r2=1.3)
        resqueue.c (r1.1 -> r1.2)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/resscheduler/resqueue.c.diff?r1=1.1&r2=1.2)
        resscheduler.c (r1.1 -> r1.2)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/resscheduler/resscheduler.c.diff?r1=1.1&r2=1.2)
    bizgres/postgresql/src/include/storage:
        lock.h (r1.2 -> r1.3)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/include/storage/lock.h.diff?r1=1.2&r2=1.3)
        lwlock.h (r1.2 -> r1.3)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/include/storage/lwlock.h.diff?r1=1.2&r2=1.3)
        proc.h (r1.2 -> r1.3)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/include/storage/proc.h.diff?r1=1.2&r2=1.3)
    bizgres/postgresql/src/include/utils:
        resscheduler.h (r1.1 -> r1.2)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/include/utils/resscheduler.h.diff?r1=1.1&r2=1.2)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Add new return codes SPI_OK_INSERT_RETURNING etc to the SPI API.
Next
From: petere@postgresql.org (Peter Eisentraut)
Date:
Subject: pgsql: Turn autovacuum on by default.