Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 7532C9FB91C for ; Tue, 31 Jul 2007 05:02:57 -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 54194-06 for ; Tue, 31 Jul 2007 05:02: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 AFB649FB61D for ; Tue, 31 Jul 2007 05:02:53 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id k40so2348043wah for ; Tue, 31 Jul 2007 01:02:52 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=X6o48dC7o7iiYS5GFnU+TdH0U3o/CRdNwoaguNzop6X+KjgFxQnsGleZ0mGdC20bDGdcRDi/+NC3kyCpFyL+yk3sBUgiuXVxNpLTDuf/Wn7YZ2gE3+q4z/LqB3HVO7/EiovILNqnGaJcCat1Gx0vhzfoCdP68Ym41pF0TZyMRWM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=LkDupgU+kLVKaM0e7brLar5y6BQqA5DwBVlbn569TY7D+0TmcnGR2edYb0pmW+w2chuev99dZ/gC6AyiTfUZwonTGOFzPMQuziFnre2GOOpwun7sQP8m2N/f+Up3i70v2XBORBqk98D9JWsrQuwH88lEaZl5ymWldepO39nz3fQ= Received: by 10.114.171.1 with SMTP id t1mr6425075wae.1185868972305; Tue, 31 Jul 2007 01:02:52 -0700 (PDT) Received: by 10.114.234.2 with HTTP; Tue, 31 Jul 2007 01:02:52 -0700 (PDT) Message-ID: <6c3fb5eb0707310102s73bf7516w8dd157c550e2cf7d@mail.gmail.com> Date: Tue, 31 Jul 2007 13:32:52 +0530 From: "Jyoti Seth" To: "Richard Huxton" Subject: Re: Database synchronization Cc: pgsql-sql@postgresql.org In-Reply-To: <001e01c7cf40$85e7b540$91b71fc0$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_42518_15748223.1185868972271" References: <20070724143737.GA25948@apartia.fr> <004e01c7cea4$58046570$080d3050$@com> <46A724CB.3030405@archonet.com> <000001c7cea8$39775d20$ac661760$@com> <46A7449A.4080500@archonet.com> <001e01c7cf40$85e7b540$91b71fc0$@com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/194 X-Sequence-Number: 28929 ------=_Part_42518_15748223.1185868972271 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, I have one query related to slony-I. Can I replicate table data in different schemas. Say if have table 'country' in database 'stock' and schema 'stocksch'. And I want to replicate the data in table 'country' of database 'smsdb' and schema 'smssch'. Here, the country table is present in two different schemas. Can I replicate the country table data from schema stocksch to schema smssch or I have to create a schema with the same name for replication. Thanks, Jyoti Seth On 7/26/07, Jyoti Seth wrote: > > 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 > > ------=_Part_42518_15748223.1185868972271 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hello,
 
I have one query related to slony-I. Can I replicate table data in different schemas. Say if have table 'country' in database 'stock' and schema 'stocksch'. And I want to replicate the data in table 'country' of database 'smsdb' and schema 'smssch'. Here, the country table is present in two different schemas. Can I replicate the country table data from schema stocksch to schema smssch or I have to create a schema with the same name for replication.
 
Thanks,
Jyoti Seth

 
On 7/26/07, Jyoti Seth <jyotiseth2001@gmail.com> wrote:
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


------=_Part_42518_15748223.1185868972271--