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

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cascading replication: should we detect/prevent cycles?
Date: 2012-12-19 07:57:07
Message-ID: CA+U5nMKq6qkfNtAYzM6LyAyefBLT+QJWC7ot+8ZnoNQ3xV1KXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-12-19 07:59:57 Re: Feature Request: pg_replication_master()
Previous Message Shigeru Hanada 2012-12-19 06:39:00 Re: proposal - assign result of query to psql variable