Re: Cascading replication: should we detect/prevent cycles?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Joshua Berkus <josh(at)agliodbs(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: Cascading replication: should we detect/prevent cycles?
Date: 2012-12-20 13:04:12
Message-ID: CA+TgmoasrWoFpZW25YV+5FFx+CrSMQL9dbptsXQrb7XkwXkzuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 19, 2012 at 5:14 PM, Joshua Berkus <josh(at)agliodbs(dot)com> wrote:
> What would such a test look like? It's not obvious to me that there's any rapid way for a user to detect this situation, without checking each server individually.

Change something on the master and observe that none of the supposed
standbys notice?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2012-12-20 13:19:37 Re: ThisTimeLineID in checkpointer and bgwriter processes
Previous Message Robert Haas 2012-12-20 13:00:47 Re: Parser Cruft in gram.y