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+o-cJa3K6t5QySbf2FeenQx1OuZpHEhByMuz-g9jBAfw@mail.gmail.com
Whole thread Raw
In response to Re: Cascading replication: should we detect/prevent cycles?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Cascading replication: should we detect/prevent cycles?
List pgsql-hackers
On 8 January 2013 18:46, Josh Berkus <josh@agliodbs.com> wrote:
> 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?

Daniel already did object....

I think we have other problems that need solving much more than this.

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it
Next
From: Tom Lane
Date:
Subject: Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it