Re: Disabled features on Hot Standby

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Disabled features on Hot Standby
Date: 2012-01-13 15:17:14
Message-ID: CA+U5nM+f_qdKiktgY-amu7SUYg6cWDsvnjocP3Dab9zH+vD3SQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-13 15:21:22 show Heap Fetches in EXPLAIN for index-only scans
Previous Message Robert Haas 2012-01-13 14:03:49 Re: Disabled features on Hot Standby