Skip site navigation (1) Skip section navigation (2)

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

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: Cascading replication: should we detect/prevent cycles?
Date: 2013-01-08 18:46:12
Message-ID: 50EC6974.2080108@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 1/5/13 1:21 PM, Peter Geoghegan wrote:
> On 21 December 2012 14:08, Robert Haas <robertmhaas(at)gmail(dot)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


In response to

Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2013-01-08 19:09:42
Subject: [PATCH] xlogreader-v4
Previous:From: Tom LaneDate: 2013-01-08 18:08:44
Subject: pg_upgrade regression test litters the source tree with log files

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group