Received: from localhost (maia-2.hub.org [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id 12A2C9FBAB6
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 26 Jul 2007 02:13:38 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024)
	with ESMTP id 61687-04 for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 26 Jul 2007 02:12:28 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5
Received: from py-out-1112.google.com (py-out-1112.google.com
 [64.233.166.181])
	by postgresql.org (Postfix) with ESMTP id 27BC49FB95E
	for <pgsql-sql@postgresql.org>; Thu, 26 Jul 2007 02:00:47 -0300 (ADT)
Received: by py-out-1112.google.com with SMTP id d32so976192pye
	for <pgsql-sql@postgresql.org>; Wed, 25 Jul 2007 22:00:46 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:from:to:cc:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=aJGspnAOKPYvaip5DNZGaRf+LRnFMoI04zyKWvVVYqfCL1oWqtppQPw2ZZhbjL7gvI9WID0y6uvCNm3reAr4zJblBGyF6GYLLw4kUfN2dIJRWuG01zn9Ao7dZ+U6xBnJPThbOzfRgn7PapJ4xsMuN3LMhDpVzXvBG7bLzT7Ru4Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:from:to:cc:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=Bdg3XY79cHWYlTXX3r+C6CVeWj6OwubG3Bo0T9TUvYHGph8zW5pROVFNi5eHZTI4zaTwy8taiyGCxtRISw65SGgXU+enJsgCCDfNYVDGK+Kfa5TQMM1yDb3QuQLB3UqMFS9/danANyxNmTGpzKhGgqCE8m1+HD2izS5UajXO2ew=
Received: by 10.140.186.18 with SMTP id j18mr441124rvf.1185425621169;
	Wed, 25 Jul 2007 21:53:41 -0700 (PDT)
Received: from bitdldt04 ( [122.162.167.88])
	by mx.google.com with ESMTPS id g31sm2407918rvb.2007.07.25.21.53.38
	(version=SSLv3 cipher=RC4-MD5); Wed, 25 Jul 2007 21:53:40 -0700 (PDT)
From: "Jyoti Seth" <jyotiseth2001@gmail.com>
To: "'Richard Huxton'" <dev@archonet.com>
Cc: <pgsql-sql@postgresql.org>
References: <20070724143737.GA25948@apartia.fr>
	<004e01c7cea4$58046570$080d3050$@com>
	<46A724CB.3030405@archonet.com>
	<000001c7cea8$39775d20$ac661760$@com>
	<46A7449A.4080500@archonet.com>
In-Reply-To: <46A7449A.4080500@archonet.com>
Subject: Re: Database synchronization
Date: Thu, 26 Jul 2007 10:20:39 +0530
Message-ID: <001e01c7cf40$85e7b540$91b71fc0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcfOuUZ5jMjSi1wuS5m/QUgrMTDbHAAhw3zg
Content-Language: en-us
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200707/150
X-Sequence-Number: 28885

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