<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 01/23/14 20:30, Syed Irfan wrote:<br>
</div>
<blockquote
cite="mid:WM!1e7abf70bfc2fb0bd94fc4c39e74de2702fc04448af1d3518c2ccc032333f1dbc25f5a7ef77beb6f366e387da5000d99!@asav-3.01.com"
type="cite">
<div style="background-color: transparent;">rsync -C -a -c
--delete --exclude postgresql.conf --exclude postmaster.pid \</div>
<div style="background-color: transparent;">--exclude
postmaster.opts --exclude pg_log \</div>
<div style="background-color: transparent;">--exclude
recovery.conf --exclude recovery.done \</div>
<div style="background-color: transparent;">--exclude pg_xlog \</div>
<div style="background-color: transparent;">$master_db_cluster/
$recovery_node_host_name:$recovery_db_cluster</div>
</blockquote>
<br>
So, is the $recovery_db_cluster on the replica node empty when the
base backup starts? It seems like it might have had some WAL files
in it from a previous test.<br>
<br>
I think because you're excluding pg_xlog, rsync doesn't process the
--deletes on it, so you need to make sure and clean it out on the
replica if there were any existing WAL files before starting
postgres.<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="78">--
Jeff Frost <a class="moz-txt-link-rfc2396E" href="mailto:jeff@pgexperts.com"><jeff@pgexperts.com></a>
CTO, PostgreSQL Experts, Inc.
Phone: 1-888-PG-EXPRT x506
FAX: 415-762-5122
<a class="moz-txt-link-freetext" href="http://www.pgexperts.com/">http://www.pgexperts.com/</a>
</pre>
</body>
</html>