Re: High-availability - Mailing list pgsql-general

From Lew
Subject Re: High-availability
Date
Msg-id UNadncwsObXRZv_bnZ2dnUVZ_qarnZ2d@comcast.com
Whole thread Raw
In response to Re: High-availability  ("Alexander Staubo" <alex@purefiction.net>)
List pgsql-general
Alexander Staubo wrote:
>> As a side-note, I sat up pgpool-II today, and was pleasantly surprised
>> about how easy it all was; within two minutes I had two databases in
>> perfect sync on my laptop. It has limitations (such as in its handling
>> of sequences), but compared to Slony it's like a breath of fresh
>> mountain air.
>
> Err, the setup is, I mean. Once you have Slony up and running, it's
> pretty smooth.

I wonder what the OP means by "real-time".  The standard definition is "within
a deterministic time bound".

Replication implies latency.  Ignoring latency or wishing it away will not help.

It is possible to manage latency.  One strategy is to minimize it.  There are
others.

Also remember the ancient proverb, applicable when two or more nodes are
trying to agree on what time it is:
"Man with two watches never knows correct time."

I think of this category of issue as the Special Relativity of information.

--
Lew

pgsql-general by date:

Previous
From: Lew
Date:
Subject: Re: Delete with subquery deleting all records
Next
From: Lew
Date:
Subject: Re: There can be only one! How to avoid the "highlander-problem".