Re: Hot standby and b-tree killed items - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Hot standby and b-tree killed items
Date
Msg-id 873agjly1j.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Hot standby and b-tree killed items  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot standby and b-tree killed items  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:

> Increasing the waiting time increases the failover time and thus
> decreases the value of the standby as an HA system. Others value high
> availability higher than you and so we had agreed to provide an option
> to allow the max waiting time to be set.

Sure, it's a nice option to have. But I think the default should be to pause
WAL replay.

The question I had was whether your solution for btree pointers marked dead
and later dropped from the index works when the user hasn't configured a
timeout and doesn't want standby queries killed.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot standby and b-tree killed items
Next
From: Gregory Stark
Date:
Subject: Re: Hot standby and b-tree killed items