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

From Simon Riggs
Subject Re: Review: Hot standby
Date
Msg-id 1227895239.20796.232.camel@hp_dx2400_1
Whole thread Raw
In response to Re: Review: Hot standby  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 2008-11-28 at 12:45 -0500, Tom Lane wrote:
> 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?

Yes, that is by far the best solution. ISTM many people will be happy.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Review: Hot standby
Next
From: Tom Lane
Date:
Subject: Re: A bug with ALTER TABLE SET WITHOUT OIDS in CVS HEAD