Skip site navigation (1) Skip section navigation (2)

pgsql: Re-enable max_standby_delay = -1 using deadlock detection on

From: sriggs(at)postgresql(dot)org (Simon Riggs)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Re-enable max_standby_delay = -1 using deadlock detection on
Date: 2010-02-13 01:32:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Re-enable max_standby_delay = -1 using deadlock detection on startup
process. If startup waits on a buffer pin we send a request to all
backends to cancel themselves if they are holding the buffer pin
required and they are also waiting on a lock. If not, startup waits
until max_standby_delay before cancelling any backend waiting for
the requested buffer pin.

Modified Files:
        procsignal.c (r1.4 -> r1.5)
        standby.c (r1.11 -> r1.12)
        proc.c (r1.215 -> r1.216)
        postgres.c (r1.587 -> r1.588)
        guc.c (r1.538 -> r1.539)
        proc.h (r1.119 -> r1.120)
        procsignal.h (r1.4 -> r1.5)
        standby.h (r1.7 -> r1.8)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-02-13 02:34:16
Subject: pgsql: Support inlining various small performance-critical functions on
Previous:From: Simon RiggsDate: 2010-02-13 00:59:58
Subject: pgsql: Introduce WAL records to log reuse of btree pages, allowing

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group