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

From: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Joshua Berkus <josh(at)agliodbs(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-05 21:21:11
Message-ID: CAEYLb_US_+B8fZ2_biXdOUD4DYDpH0Hqub4LPmR_mdK7uO_Fmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-01-05 22:18:16 Re: [PERFORM] Slow query: bitmap scan troubles
Previous Message Joshua Berkus 2013-01-05 20:50:05 Re: Cascading replication: should we detect/prevent cycles?