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

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cascading replication: should we detect/prevent cycles?
Date: 2012-12-19 08:11:55
Message-ID: 50D176CB.3050008@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 12/18/2012 11:57 PM, Simon Riggs wrote:
>
> On 19 December 2012 03:03, Josh Berkus <josh(at)agliodbs(dot)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.

>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-12-19 08:34:15 Re: Cascading replication: should we detect/prevent cycles?
Previous Message Simon Riggs 2012-12-19 08:08:26 Re: system administration functions with hardcoded superuser checks