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

From Simon Riggs
Subject Re: Cascading replication: should we detect/prevent cycles?
Date
Msg-id CA+U5nM+Pwonwy8CcPFi6WyKK04LP5a82Z6oKWhn6=ELwovKrUQ@mail.gmail.com
Whole thread Raw
In response to Re: Cascading replication: should we detect/prevent cycles?  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Cascading replication: should we detect/prevent cycles?  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Cascading replication: should we detect/prevent cycles?  (Joshua Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 19 December 2012 08:11, Joshua D. Drake <jd@commandprompt.com> wrote:
>
> On 12/18/2012 11:57 PM, Simon Riggs wrote:
>>
>>
>> On 19 December 2012 03:03, Josh Berkus <josh@agliodbs.com> wrote:
>>
>>> So, my question is:
>>>
>>> 1. should we detect for replication cycles?  *Can* we?
>>> 2. should we warn the user, or refuse to start up?
>>
>>
>> Why not just monitor the config you just created? Anybody that
>> actually tests their config would spot this.
>
>
> I think you are being optimistic. We should probably have some logic that
> prevents circular replication.

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.

If you don't test your config and don't monitor either, good luck with HA.

Patches welcome, if you think this important enough.

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



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Cascading replication: should we detect/prevent cycles?
Next
From: Groshev Andrey
Date:
Subject: Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1