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+usX9=uRPMafqFX+j-WUzkx5PJaNFHtffBtnmTpBsFfQ@mail.gmail.com
Whole thread Raw
In response to Re: Cascading replication: should we detect/prevent cycles?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 9 January 2013 01:51, Josh Berkus <josh@agliodbs.com> wrote:

> Anyway, I'm not saying we solve this now.  I'm saying, "put it on the
> TODO list in case someone has time/an itch to scratch".

I think its reasonable to ask whether a usability feature needs to
exist whenever a problem is encountered. That shouldn't need to
translate to a new feature/TODO every time we ask the question though.

IMHO, in this case, we should document this as an issue that can
happen and we should caution that careful testing is required.

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



pgsql-hackers by date:

Previous
From: "emergency.shower@gmail.com"
Date:
Subject: Bug: Windows installer modifies ACLs on the whole volume
Next
From: Amit Kapila
Date:
Subject: Re: Extra XLOG in Checkpoint for StandbySnapshot