Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 788702E317B for ; Fri, 28 Dec 2007 05:22:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 31855-05 for ; Fri, 28 Dec 2007 05:22:17 -0400 (AST) Received: from base.wars-nicht.de (wars-nicht.de [213.239.199.195]) by postgresql.org (Postfix) with ESMTP id 4A9812E316D for ; Fri, 28 Dec 2007 05:22:21 -0400 (AST) Received: from iridium.wars-nicht.de (Qd938.q.pppool.de [89.53.217.56]) by base.wars-nicht.de (Postfix) with ESMTP id 08F17784179 for ; Fri, 28 Dec 2007 10:22:18 +0100 (CET) Received: from iridium.wars-nicht.de (iridium.wars-nicht.de [127.0.0.1]) by iridium.wars-nicht.de (Postfix) with ESMTP id CCA5F3DC965 for ; Fri, 28 Dec 2007 10:22:01 +0100 (CET) Date: Fri, 28 Dec 2007 10:22:01 +0100 From: Andreas 'ads' Scherbaum To: pgsql-admin@postgresql.org Subject: Re: Fresh copy of a PG DB ? Message-ID: <20071228102201.6e6ae6e9@iridium.wars-nicht.de> In-Reply-To: <4774BE99.9010602@tatm.com> References: <4774BE99.9010602@tatm.com> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.12.0; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/228 X-Sequence-Number: 27745 Hello, On Fri, 28 Dec 2007 10:15:05 +0100 Pascal Heraud wrote: > What are the other solution to provide this service in a incremental > manner ? Is there any "dupplication" tool or mechanism provided to allow > such a repplication ? One solution is "Slony" to replicate tables to another database. Or you can use PITR do copy every WAL logfile to your second machine and apply all changes as far as you have logfiles. > We looked at the way of using a replication solution but it seems very > coupled to the version of the database we use. We are using PGSQL 8.2.4 > on a Gentoo Linux OS. Uh? At least a replication with PITR is straightforward, some config modifications, a script to archive the logfile, one to restore the logfile and something to transfer the logfile to your other machine. Basically, that should be all you need. Not so long ago i created such a setup and the replication itself was the easy part. It got much worse the time we had to integrate the replication into RH cluster software. Kind regards -- Andreas 'ads' Scherbaum German PostgreSQL User Group