From: twinsen <twins3n@yahoo.com>
To: pgsql-admin@postgresql.org
Subject: Reliable database communication - Slightly OT
Date: Mon, 24 May 2004 12:07:03 -0700 (PDT)
Message-ID: <20040524190703.47097.qmail@web41405.mail.yahoo.com> (raw)
Hi all
I have an architecture 'problem' which I would like to
bounce off you. We have five remote Interactive Voice
Response sites interconnected via WAN links. I have
two Postgresql databases replicated at one of the
sites. I need to capture data (mostly stats) from the
IVR's and store the data in one of the databases - or
both in which case I could drop replication.
What messaging methods could one use to ensure data is
never lost if a link should go down? I need something
that would detect failure and buffer or something like
that. A simple connection to the database wont cut it
- then again, maybe one of you has found a way.
I am reading through the spread www.spread.org docs
already, but maybe one of you has had experience with
a situation like this?
Kind Regards
Craig
__________________________________
Do you Yahoo!?
Yahoo! Domains Claim yours for only $14.70/year
http://smallbusiness.promotions.yahoo.com/offer
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-admin@postgresql.org
Cc: twins3n@yahoo.com
Subject: Re: Reliable database communication - Slightly OT
In-Reply-To: <20040524190703.47097.qmail@web41405.mail.yahoo.com>
References: <20040524190703.47097.qmail@web41405.mail.yahoo.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