pgsql: Detect early deadlock in Hot Standby when Startup is already

From: sriggs(at)postgresql(dot)org (Simon Riggs)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Detect early deadlock in Hot Standby when Startup is already
Date: 2010-01-31 19:01:11
Message-ID: 20100131190111.5880C7541B9@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-01-31 19:07:47 Re: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to
Previous Message Tom Lane 2010-01-31 18:15:39 pgsql: Fix memory leak created by deferrable-index-constraints patches.