Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id E2D641337B69
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  9 Feb 2011 10:28:24 -0400 (AST)
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 80590-01 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  9 Feb 2011 14:28:17 +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 8E03C133616B
	for <pgsql-admin@postgresql.org>; Wed,  9 Feb 2011 10:28:17 -0400 (AST)
Received: by locust.cns.vt.edu (Postfix, from userid 986)
	id 1EC37118E08; Wed,  9 Feb 2011 09:28:18 -0500 (EST)
Date: Wed, 9 Feb 2011 09:28:18 -0500
From: Ray Stell <stellr@cns.vt.edu>
To: pgsql-admin@postgresql.org
Subject: Re: PostgreSQL 9.0.3 streaming replication failure
Message-ID: <20110209142818.GA30017@cns.vt.edu>
References: <20110209135548.GA27471@cns.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110209135548.GA27471@cns.vt.edu>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=2.409 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	FS_REPLICA=3.599, SARE_SPEC_REPLICA=0.72,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: **
X-Archive-Number: 201102/52
X-Sequence-Number: 36691

On Wed, Feb 09, 2011 at 08:55:48AM -0500, Ray Stell wrote:
> I had set up this streaming replication pair of systems a few days ago and
> everything seemed pretty happy as changes were being replicated.  I set
> it up without wal archiving turned up.  The backup log this morning caught
> my eye.  I find the standby reports to have activated itself. 
> 
> I don't see anything in the postmaster logs on this event.
> 
> The backup log caught my eye:
> -------------------------------
>  pg_start_backup 
> -----------------
>  1/E0000020
> (1 row)
> 
> NOTICE:  WAL archiving is not enabled; you must ensure that all required WAL segments are copied through other means to complete the backup
>  pg_stop_backup 
> ----------------
>  1/E00000C4
> (1 row)


my bad, this was a path issue, I was using a v8 pg_controldata cmd.
the v9 pg_controldata looks good.  Sorry.

This does not explain the backup/wal archive msg, however.  Is that
msg normal for a streaming rep set up?