Re: Cascading replication: should we detect/prevent cycles? - Mailing list pgsql-hackers

From Joshua Berkus
Subject Re: Cascading replication: should we detect/prevent cycles?
Date
Msg-id 610689608.118643.1355955296853.JavaMail.root@agliodbs.com
Whole thread Raw
In response to Re: Cascading replication: should we detect/prevent cycles?  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Cascading replication: should we detect/prevent cycles?
List 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



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: strange OOM errors with EXECUTE in PL/pgSQL
Next
From: Joshua Berkus
Date:
Subject: Re: Feature Request: pg_replication_master()