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
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
