From: Richard Huxton <dev@archonet.com>
To: Jyoti Seth <jyotiseth2001@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Database synchronization
Date: Wed, 25 Jul 2007 13:39:54 +0100
Message-ID: <46A7449A.4080500@archonet.com> (raw)
In-Reply-To: <000001c7cea8$39775d20$ac661760$@com>
References: <20070724143737.GA25948@apartia.fr>
<004e01c7cea4$58046570$080d3050$@com>
<46A724CB.3030405@archonet.com>
<000001c7cea8$39775d20$ac661760$@com>
Jyoti Seth wrote:
> My master database contains prices of some products that vary after few
> hours and many other details that are also reqd in Db2 which doesn't change
> that frequently. My slave database contains the details of queries sent by
> the customers.
> These queries are to find the price of the product and other details. (Some
> part of the info reqd from Db1 varies frequently where some information is a
> kind of master data that doesn't vary frequently).
>
> So should I use all the ways i.e #2 or #3 to get price info and #1 (slony)
> for other details or there is some other better option
If you can live with a time-lag measured in seconds, then slony will
work just fine. If you can't then you'll want dblink.
One other thing you might consider - if you attach "valid_from" time to
each price then you can put them in place in advance, and make sure they
are replicated before needed.
--
Richard Huxton
Archonet Ltd
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dev@archonet.com, jyotiseth2001@gmail.com
Subject: Re: Database synchronization
In-Reply-To: <46A7449A.4080500@archonet.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