X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D109814B280B for ; Tue, 10 Aug 2004 12:10:39 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 15712-08 for ; Tue, 10 Aug 2004 15:10:28 +0000 (GMT) Received: from snowwhite.lulu.com (mail.lulu.com [66.193.5.50]) by svr1.postgresql.org (Postfix) with ESMTP id ADED514B281A for ; Tue, 10 Aug 2004 12:10:24 -0300 (ADT) Received: from [10.0.0.32] (meatwad.rdu.lulu.com [10.0.0.32]) (authenticated bits=0) by snowwhite.lulu.com (8.12.8/8.12.8) with ESMTP id i7AFA9QR004391 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 10 Aug 2004 11:10:09 -0400 Message-ID: <4118E55B.20002@lulu.com> Date: Tue, 10 Aug 2004 11:10:19 -0400 From: Bill Montgomery User-Agent: Mozilla Thunderbird 0.7 (X11/20040615) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rodrigo Botana , pgsql-admin@postgresql.org Subject: Re: Replication References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/60 X-Sequence-Number: 14455 Rodrigo, Rodrigo Botana wrote: > There is any way to have a replication (master -> slave) whithout > install anything on the slave computer. I ask this because i would > like to have my website (that don't have any replication service > avaliable) with the same information of my internal system. In theory, the slon daemon of Slony-I (http://slony.info/) can be run on a separate machine from the database to which it connects (it just uses a libpq connection). With this technique, you could run the website's slon daemon on your local box, along with the slon daemon for the "master" database. YMMV on how well it works with the slon-->postmaster connection over a WAN (it is typically over a local socket). Depending on your requirements, however, Slony may be overkill. What is the size of your data set? How many seconds/minutes/hours/days can your website afford to be out of sync with the data on your internal system? If you could be as much as say, a day out of date, and your data set is less than 100MB, and you have a pretty fast connection between your internal system and the website, you might get away with a nightly pg_dump, piped to a psql process that connects to the pgsql server on your website. There are many ways to skin the replication cat, and the right one depends on your requirements. There is no one universal solution that's appropriate for everyone, but with more information, we could be of better help. Best Regards, Bill Montgomery