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

From: Joshua Berkus <josh(at)agliodbs(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: 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-19 22:14:56
Message-ID: 610689608.118643.1355955296853.JavaMail.root@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon,

> My logic is that if you make a 1 minute test you will notice your
> mistake, which is glaringly obvious. That is sufficient to prevent
> that mistake, IMHO.

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.

If there's a quick and easy way to test for cycles from the user side, we should put it in documentation somewhere.

--Josh

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua Berkus 2012-12-19 22:19:54 Re: Feature Request: pg_replication_master()
Previous Message Tomas Vondra 2012-12-19 22:09:41 strange OOM errors with EXECUTE in PL/pgSQL