From: Chris Travers <chris@travelamericas.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: Ron Johnson <ron.l.johnson@cox.net>
Cc: pgsql-general@postgresql.org
Subject: Re: Replication Ideas
Date: Mon, 25 Aug 2003 15:15:25 -0700
Message-ID: <3F4A8A7D.30308@travelamericas.com> (raw)
In-Reply-To: <11627.1061845759@sss.pgh.pa.us>
References: <3F483EBD.3020108@travelamericas.com>
<1061705587.3733.452.camel@haggis>
<3F4A420E.6090604@travelamericas.com>
<20030825182441.GB9597@dcc.uchile.cl>
<3F4A5724.3060002@travelamericas.com>
<11627.1061845759@sss.pgh.pa.us>
Tom Lane wrote:
>Chris Travers <chris@travelamericas.com> writes:
>
>
>>Yes I have. Postgres-r is not a high-availability solution which is
>>capable of transparent failover,
>>
>>
>
>What makes you say that? My understanding is it's supposed to survive
>loss of individual servers.
>
> regards, tom lane
>
>
>
>
My mistake. I must have gotten them confused with another
(asynchronous) replication project.
Best Wishes,
Chris Travers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: chris@travelamericas.com, tgl@sss.pgh.pa.us, alvherre@dcc.uchile.cl, ron.l.johnson@cox.net, pgsql-general@postgresql.org
Subject: Re: Replication Ideas
In-Reply-To: <3F4A8A7D.30308@travelamericas.com>
References: <3F483EBD.3020108@travelamericas.com> <1061705587.3733.452.camel@haggis> <3F4A420E.6090604@travelamericas.com> <20030825182441.GB9597@dcc.uchile.cl> <3F4A5724.3060002@travelamericas.com> <11627.1061845759@sss.pgh.pa.us> <3F4A8A7D.30308@travelamericas.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox