Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 6F5E263534B
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu,  5 Mar 2009 15:53:35 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 23841-04-3
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu,  5 Mar 2009 15:53:33 -0400 (AST)
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 1971D63544E
	for <pgsql-admin@postgresql.org>; Thu,  5 Mar 2009 15:52:51 -0400 (AST)
Received: by locust.cns.vt.edu (Postfix, from userid 986)
	id CD046118DDE; Thu,  5 Mar 2009 14:52:49 -0500 (EST)
Date: Thu, 5 Mar 2009 14:52:49 -0500
From: Ray Stell <stellr@cns.vt.edu>
To: Yauheni Labko <yyl@chappy.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: standby waiting for what?
Message-ID: <20090305195249.GC1068@cns.vt.edu>
References: <20090304200612.GA25611@cns.vt.edu>
	<200903041705.19794.yyl@chappy.com>
	<20090305135556.GA9900@cns.vt.edu>
	<200903051004.44932.yyl@chappy.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200903051004.44932.yyl@chappy.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200903/79
X-Sequence-Number: 31579

On Thu, Mar 05, 2009 at 10:04:44AM -0500, Yauheni Labko wrote:
> You gave the recovery command, not the archive command.  

I'm curious why you are focused on the archive on the primary?
Is there some logic in the archive process that could cause the recovery to 
be looking for /data/pgsql/wals/alerts_oamp/00000002000000000000001C.00512178.backup ?
That doesn't make any sense to me.  Are they not two completely seperate
worlds or does the archive command somehow determine what 
args go pg_standby? 

The archive command is set to:
archive_command = '/home/postgresql/bin/archive.sh %p %f alerts_oamp' 

that script in essence echos some debug values and rsyncs the WAL file
over.

echo "src - $SRC"
echo "destname - $NAME"
rsync --links -e 'ssh -c blowfish -ax' -avz "${SRC}" "${STBY}:${STBYDIR}/${NAME}"

Again, those files look fine on the standby, the names are identical to 
those in the primary pg_xlogs.  So, please explain your reasoning.


> And give a piece of 
> log file where primary server performs archiving WAL files.


src - /data/pgsql/alerts_oamp/pg_xlog/00000002000000000000001F
destname - 00000002000000000000001F
Authorized use only!  All sessions may be monitored or recorded.
building file list ... done
00000002000000000000001F

sent 4211135 bytes  received 42 bytes  935817.11 bytes/sec
total size is 16777216  speedup is 3.98
src - /data/pgsql/alerts_oamp/pg_xlog/000000020000000000000020
destname - 000000020000000000000020
Authorized use only!  All sessions may be monitored or recorded.
building file list ... done
000000020000000000000020

sent 4750728 bytes  received 42 bytes  863776.36 bytes/sec
total size is 16777216  speedup is 3.53