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

From Josh Berkus
Subject Re: Cascading replication: should we detect/prevent cycles?
Date
Msg-id 50EC6974.2080108@agliodbs.com
Whole thread Raw
In response to Re: Cascading replication: should we detect/prevent cycles?  (Peter Geoghegan <peter@2ndquadrant.com>)
Responses Re: Cascading replication: should we detect/prevent cycles?
Re: Cascading replication: should we detect/prevent cycles?
List pgsql-hackers
On 1/5/13 1:21 PM, Peter Geoghegan wrote:
> On 21 December 2012 14:08, Robert Haas <robertmhaas@gmail.com> wrote:
>> I'm sure it's possible; I don't *think* it's terribly easy.
>
> I'm inclined to agree that this isn't a terribly pressing issue.
> Certainly, the need to introduce a bunch of new infrastructure to
> detect this case seems hard to justify.

Impossible to justify, I'd say.

Does anyone have any objections to my adding this to the TODO list, in 
case some clever GSOC student comes up with a way to do it *without* 
adding a bunch of infrastructure?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: pg_upgrade regression test litters the source tree with log files
Next
From: Andres Freund
Date:
Subject: [PATCH] xlogreader-v4