Log Message:
-----------
Fix self (dead)lock check to work correctly - iterate through my portals and
see if I have total increments higher than any corresponding thresholds.
Modified Files:
--------------
bizgres/postgresql/src/backend/storage/lmgr:
proc.c (r1.9 -> r1.10)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/storage/lmgr/proc.c.diff?r1=1.9&r2=1.10)
bizgres/postgresql/src/backend/utils/mmgr:
portalmem.c (r1.6 -> r1.7)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/mmgr/portalmem.c.diff?r1=1.6&r2=1.7)
bizgres/postgresql/src/backend/utils/resscheduler:
resqueue.c (r1.14 -> r1.15)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/backend/utils/resscheduler/resqueue.c.diff?r1=1.14&r2=1.15)
bizgres/postgresql/src/include/utils:
portal.h (r1.6 -> r1.7)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/include/utils/portal.h.diff?r1=1.6&r2=1.7)
resscheduler.h (r1.12 -> r1.13)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/src/include/utils/resscheduler.h.diff?r1=1.12&r2=1.13)
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
