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

From: Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cascading replication: should we detect/prevent cycles?
Date: 2013-02-01 07:43:03
Message-ID: CAEYLb_W3fYBRcH6rQLkTjGjFjQ8HgpoTOJB3E+rgK=WDcu+Jvw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, 27 January 2013, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> If we're going to start installing safeguards against doing stupid
> things, there's a long list of scenarios that happen far more
> regularly than this ever will and cause far more damage.

+1

--
Regards,
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeevan Chalke 2013-02-01 08:01:31 Re: pg_dump --pretty-print-views
Previous Message Pavel Stehule 2013-02-01 05:37:39 Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used