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

From Joshua D. Drake
Subject Re: Cascading replication: should we detect/prevent cycles?
Date
Msg-id 50D1F4AB.7010705@commandprompt.com
Whole thread Raw
In response to Re: Cascading replication: should we detect/prevent cycles?  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On 12/19/2012 12:34 AM, Simon Riggs wrote:

> My logic is that if you make a 1 minute test you will notice your
> mistake, which is glaringly obvious. That is sufficient to prevent
> that mistake, IMHO.
>
> If you don't test your config and don't monitor either, good luck with HA.

I am not arguing whether you are right. I am arguing whether or not we 
want to shoot all but our experts users in the foot. People make 
mistakes, when reasonable we should help them not make those mistakes.

JD



-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [ADMIN] Problems with enums after pg_upgrade
Next
From: Robert Haas
Date:
Subject: Re: Set visibility map bit after HOT prune