| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Jyoti Seth <jyotiseth2001(at)gmail(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Database synchronization |
| Date: | 2007-07-25 12:39:54 |
| Message-ID: | 46A7449A.4080500@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Lambert | 2007-07-25 22:29:10 | Assistance with a trigger |
| Previous Message | Jyoti Seth | 2007-07-25 10:40:27 | Re: Database synchronization |