From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | David Garamond <lists(at)zara(dot)6(dot)isreserved(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: shadowing (like IB/Firebird) |
Date: | 2004-04-27 03:43:00 |
Message-ID: | 200404270343.i3R3h0R28023@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
David Garamond wrote:
> >>Now suppose /disk1 fails, one of the shadow can be configured to
> >>immediately take over as the master database, without any down time. We
> >>can then add /disk4/dbname.fdb, for instance, to become a new shadow.
> >>
> >>Alternatively, when a shadow fails, IB/Firebird can refuse further
> >>transactions until there is another shadow coming up, so the database is
> >>shadowed all the time.
> >
> > No, we don't have plans to do that. We will allow continuous logging so
> > a tar backup plus this log will bring you up to current.
>
> What about the future synchronous replication or clustering? Will this
> feature do what shadowing in IB/FB does? Cause I've met a couple of
> people that really love this feature and they cling to FB because of this.
>
> Actually, what is needed is:
>
> - an exact mirror at all times;
> - a very simple, straightforward, and fast way to failover;
>
> done by software.
I recommend they keep clinging. :-)
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | wespvp | 2004-04-27 04:00:02 | Re: thread_test.c problems |
Previous Message | David Garamond | 2004-04-27 03:39:52 | Re: shadowing (like IB/Firebird) |