X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id AD95D9DCAB5 for ; Mon, 12 Dec 2005 18:18:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37772-01 for ; Mon, 12 Dec 2005 18:18:45 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195]) by postgresql.org (Postfix) with ESMTP id 7A3B69DCAB1 for ; Mon, 12 Dec 2005 18:18:41 -0400 (AST) Received: by zproxy.gmail.com with SMTP id 16so864854nzp for ; Mon, 12 Dec 2005 14:18:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=l8r1lgyrj2g1dx9bYxeALvqF6iyY+hQB62QZb+m5sgTEGuV+gJVglGRqwA4K3x06LRQfBPY8muP0pNsg9ZY4UMUzWbj5Fbdmtl9IcSx4YwFD2MQuDjeZsrV8Eq+5+eMW09dfshbmhJDZtzxeH4Ep0+xvyJdU3O8Jy1/MjGdC2Eo= Received: by 10.65.157.2 with SMTP id j2mr112338qbo; Mon, 12 Dec 2005 14:18:43 -0800 (PST) Received: by 10.64.53.8 with HTTP; Mon, 12 Dec 2005 14:18:43 -0800 (PST) Message-ID: Date: Tue, 13 Dec 2005 11:18:43 +1300 From: Mike C To: pgsql-admin@postgresql.org Subject: WAL and pg_dump MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4330_27949958.1134425923608" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.322 required=5 tests=[AWL=-0.321, HTML_00_10=0.642, HTML_MESSAGE=0.001] X-Spam-Score: 0.322 X-Spam-Level: X-Archive-Number: 200512/98 X-Sequence-Number: 19818 ------=_Part_4330_27949958.1134425923608 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline All the documentation I've seen for PITR points to having to do a file system copy of sorts. Is it possible to have a weekly pg_dump and restore the database up to the last archived WAL file if the db server fails? If so, how? Is it just a matter of restoring the database then copying the archived WAL files into the xlog dir and creating a recovery.conf file? Cheers, Mike C. ------=_Part_4330_27949958.1134425923608 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline All the documentation I've seen for PITR points to having to do a file syst= em copy of sorts.

Is it possible to have a weekly pg_dump and restore the database up to the last archived WAL file if the db server fails? If so, how? Is it just a matter of restoring the database then copying the archived WAL files into the xlog dir and creating a recovery.conf file?

Cheers,

Mike C.
------=_Part_4330_27949958.1134425923608--