Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id BEEB69FB68A for ; Wed, 4 Apr 2007 12:08:08 -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 38313-09 for ; Wed, 4 Apr 2007 12:07:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B821E9FB62C for ; Wed, 4 Apr 2007 12:07:56 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l34F7u38021862; Wed, 4 Apr 2007 11:07:56 -0400 (EDT) To: Damian Lubosch cc: pgsql-admin@postgresql.org Subject: Re: Hot Backup using WAL files In-reply-to: References: Comments: In-reply-to Damian Lubosch message dated "Wed, 04 Apr 2007 15:53:57 +0200" Date: Wed, 04 Apr 2007 11:07:55 -0400 Message-ID: <21861.1175699275@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/30 X-Sequence-Number: 25094 Damian Lubosch writes: > My problem now is, how to continually feed the slave server with new > received WAL files? You need to make the restore_command script wait until the next WAL file is available, instead of failing immediately. This is actually not that simple to get right. You might want to try pg_standby which will ship with 8.3: http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_standby/ regards, tom lane