| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cascading replication: should we detect/prevent cycles? |
| Date: | 2012-12-19 17:08:59 |
| Message-ID: | 50D1F4AB.7010705@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-12-19 17:10:04 | Re: Set visibility map bit after HOT prune |
| Previous Message | Andrew Dunstan | 2012-12-19 17:07:42 | Re: [ADMIN] Problems with enums after pg_upgrade |