Re: Database synchronization
От | Jyoti Seth |
---|---|
Тема | Re: Database synchronization |
Дата | |
Msg-id | 001e01c7cf40$85e7b540$91b71fc0$@com обсуждение исходный текст |
Ответ на | Re: Database synchronization (Richard Huxton <dev@archonet.com>) |
Ответы |
Re: Database synchronization
|
Список | pgsql-sql |
Thanks a lot for your suggestion. It will help me in taking the decision. -----Original Message----- From: Richard Huxton [mailto:dev@archonet.com] Sent: Wednesday, July 25, 2007 6:10 PM To: Jyoti Seth Cc: pgsql-sql@postgresql.org Subject: Re: [SQL] Database synchronization 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
В списке pgsql-sql по дате отправления: