Re: Disabled features on Hot Standby - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Disabled features on Hot Standby
Date
Msg-id CA+TgmoaxXV7k3oyy8iXCRJf+_XWQo08T=TcNg3f4mN9+Wi3CKg@mail.gmail.com
Whole thread Raw
In response to Re: Disabled features on Hot Standby  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Disabled features on Hot Standby  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Fri, Jan 13, 2012 at 10:17 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Fri, Jan 13, 2012 at 2:03 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>
>> Since the xmin horizon on the standby may precede the xmin horizon on
>> the master
>
> When hot_standby_feedback is turned on, the xmin of the standby is
> provided to the master to ensure the situation you describe never
> happens.
>
> Surely that means the problem is solved, if we can confirm the setting
> of the parameter. So this seems like a cleanup issues that can/should
> be resolved.

How do you respond to the concerns I raised about that approach in the
last sentence of my previous email?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: show Heap Fetches in EXPLAIN for index-only scans
Next
From: Magnus Hagander
Date:
Subject: Re: show Heap Fetches in EXPLAIN for index-only scans