Re: Review: Hot standby - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Review: Hot standby
Date
Msg-id 27671.1227894337@sss.pgh.pa.us
Whole thread Raw
In response to Re: Review: Hot standby  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Review: Hot standby  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Review: Hot standby  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Re: Review: Hot standby  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Fri, 2008-11-28 at 11:44 -0500, Tom Lane wrote:
>> I hadn't been following the discussion closely enough to know what the
>> problem is. 

> When we replay an AccessExclusiveLock on the standby we need to kick off
> any current lock holders, after a configurable grace period. Current
> lock holders may include some read-only backends that are
> idle-in-transaction. SIGINT, which is what the current patch uses, is
> not sufficient to dislodge the idle backends.

Hm.  People have complained of that fact from time to time in normal
usage as well.  Should we simply change SIGINT handling to allow it to
cancel an idle transaction?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Fixing contrib/isn for float8-pass-by-value
Next
From: Simon Riggs
Date:
Subject: Re: Review: Hot standby