Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id A2F2E9FBB6C for ; Thu, 19 Jul 2007 01:33:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 60234-06 for ; Thu, 19 Jul 2007 01:32:50 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by postgresql.org (Postfix) with ESMTP id 6BABA9FB8C3 for ; Thu, 19 Jul 2007 01:32:51 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id k40so556946wah for ; Wed, 18 Jul 2007 21:32:48 -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=gn8tblCUyD8SXc6Mp1TMag9SosUp0S3t9isWe3JTfF1pQTk51MRJxo000S3Q6k53ZV7L3V3oAsf2RzOR6FSTK4Ww7b+Y32UOPLTaamfJ+kFKIUwUbt+yQk5jrfFRTdKEMH550GhCyZvSLRUAdR1ICZpua4vNlpFTz6addfKJRik= 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=SkDcHXqPLmcBLbj4HSlzJ0KwbEHnBI/demYqyoJj6cM8jf/CZJeJSSPjlWHgqnXbp7CS5M0zFK4+sg4MYOk9nfEYC5L7ZM9LCUH7CRRkD1JGc3qz0kLbgMJhymhraUdK0zk/7qnBi5Y2hSn4ifjD+xVw+23OlSPFDE1zuszguUQ= Received: by 10.114.12.9 with SMTP id 9mr2196104wal.1184819567623; Wed, 18 Jul 2007 21:32:47 -0700 (PDT) Received: from bitdldt04 ( [122.162.160.164]) by mx.google.com with ESMTPS id g25sm1621800wag.2007.07.18.21.32.44 (version=SSLv3 cipher=RC4-MD5); Wed, 18 Jul 2007 21:32:46 -0700 (PDT) From: "Jyoti Seth" To: "'Richard Huxton'" Cc: References: <002d01c7c90b$48870560$d9951020$@com> <469DC124.8000704@archonet.com> <60fy3ln4ij.fsf@dba2.int.libertyrms.com> <469E3515.4070006@archonet.com> In-Reply-To: <469E3515.4070006@archonet.com> Subject: Re: Database Synchronization Date: Thu, 19 Jul 2007 10:01:14 +0530 Message-ID: <004f01c7c9bd$a657c3c0$f3074b40$@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: AcfJUuYz7IkR3a9KTQ6HckXtAchIwgAaovsg Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/119 X-Sequence-Number: 28854 Thanks a lot for your suggestions. I have ony single master. -----Original Message----- From: pgsql-sql-owner@postgresql.org [mailto:pgsql-sql-owner@postgresql.org] On Behalf Of Richard Huxton Sent: Wednesday, July 18, 2007 9:13 PM To: Chris Browne Cc: pgsql-sql@postgresql.org Subject: Re: [SQL] Database Synchronization Chris Browne wrote: > dev@archonet.com (Richard Huxton) writes: >> >> http://www.slony.info/ > But it is worth noting one thing about the synchronization... > > Slony-I's strategy is pretty simple: One node is considered the > "master," and the other node is forcibly made to conform to what is on > the master. > > If you want to synchronize back and forth (e.g. - multimaster > replication of some sort), Slony-I is not suitable... Except in the case when you can have separate tables for the data. If you have a london_sales table only updated in London and a paris_sales table only updated in Paris then you have something inching towards multi-master. -- Richard Huxton Archonet Ltd ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend