Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 353911337BD6 for ; Thu, 14 Apr 2011 22:25:08 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 92351-01 for ; Fri, 15 Apr 2011 01:25:00 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from locust.cns.vt.edu (locust.cns.vt.edu [198.82.169.14]) by mail.postgresql.org (Postfix) with ESMTP id C77091337BD5 for ; Thu, 14 Apr 2011 22:25:00 -0300 (ADT) Received: by locust.cns.vt.edu (Postfix, from userid 986) id EC269118DCF; Thu, 14 Apr 2011 21:25:00 -0400 (EDT) Date: Thu, 14 Apr 2011 21:25:00 -0400 From: Ray Stell To: pgsql-admin@postgresql.org Subject: streaming AND file-based log-shipping? Message-ID: <20110415012500.GA9121@cns.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201104/147 X-Sequence-Number: 37328 The cookbook text says, log shipping "is mostly superseded by streaming replication in 9.0, though is still useful as part of a comprehensive backup strategy." The implication is that the WAL archive might be needed for recovery in some cases: 1. Under what circumstances might the WAL archive come into play in recovery? 2. If the streaming rep fails for some reason will the standby begin recovery from the WAL archive, assuming the WAL can still be shipped? 3. What query or command set can be used to tell if file-based recovery is configured correctly if streaming replication is active? I've configured both (I think), but it isn't clear to me whether the file-based part will function. I guess I could bust the stream somehow and see what happens, but I can't find this idea documented.