pgsql: Detect early deadlock in Hot Standby when Startup is already - Mailing list pgsql-committers

From sriggs@postgresql.org (Simon Riggs)
Subject pgsql: Detect early deadlock in Hot Standby when Startup is already
Date
Msg-id 20100131190111.5880C7541B9@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Detect early deadlock in Hot Standby when Startup is already waiting. First
stage of required deadlock detection to allow re-enabling max_standby_delay
setting of -1, which is now essential in the absence of improved relation-
specific conflict resoluton. Requested by Greg Stark et al.

Modified Files:
--------------
    pgsql/src/backend/storage/ipc:
        standby.c (r1.8 -> r1.9)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/standby.c?r1=1.8&r2=1.9)
    pgsql/src/backend/storage/lmgr:
        lock.c (r1.193 -> r1.194)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lock.c?r1=1.193&r2=1.194)
    pgsql/src/include/storage:
        standby.h (r1.6 -> r1.7)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/standby.h?r1=1.6&r2=1.7)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix memory leak created by deferrable-index-constraints patches.
Next
From: richtej@pgfoundry.org (User Richtej)
Date:
Subject: pgsphere - pgsphere: # Fixes some precission problems with small