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

Re: Disabled features on Hot Standby

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Disabled features on Hot Standby
Date: 2012-01-13 15:22:20
Message-ID: CA+TgmoaxXV7k3oyy8iXCRJf+_XWQo08T=TcNg3f4mN9+Wi3CKg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Jan 13, 2012 at 10:17 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Fri, Jan 13, 2012 at 2:03 PM, Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2012-01-13 15:29:28
Subject: Re: show Heap Fetches in EXPLAIN for index-only scans
Previous:From: Robert HaasDate: 2012-01-13 15:21:22
Subject: show Heap Fetches in EXPLAIN for index-only scans

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