Hi,
My problem probably is that I need to look at the forest but am
hyper-focusing on a maple twig. I have been looking at this for 2 days now
And would appreciate some feedback...
I am running postgres 8.3.4 on master(mymachine) and slave(hummer). I am
attempting to implement warm standby.
1. On mymachine I have the following archive_command:
Scp %p postgres@hummer:/var/backups/archlog/%f
(scp has been set up with ssh keys so that password
Is not required for postgres user)
This works fine. Copies wal logs to the /var/backups/archlog directory.
2. Before I attempt pg_standby or some other wait script on hummer I have
Used a simple cp command in my recovery.conf file to manually restore
My first set of updates:
restore_command = 'cp /var/backups/archlog/%f %p'
From the doc I am assuming that %f should be the file name(s) of the
Wal log in /var/backups/archlog/ to be copied into the
/*/*/*/*/pg_xlog directory referenced by %p
But %f seems to be referencing current wal log names in
/*/*/*/*/pg_xlog. I am getting messages like:
cp: cannot stat `/var/backups/archlog/0000000600000003000000D2':
No such file or directory
0000000600000003000000D2 is an actual wal log in hummer's
/*/*/*/*/pg_xlog directory.
How do I get the %f macro to reference the file names in the
/var/backups/archlog directory?
Once I get past this, then I can play around with pg_standby and get
Real warm_standby started.
Thanks for your help,
Committed to Creating @utoEnthusiasts. Please provide us with your feedback.
________________________________
Mark Steben│Database Administrator│ @utoRevenueT
95 Ashley Ave. West Springfield, MA., 01089
413-243-4800 x1512 (Phone) │ 413-732-1824 (Fax)
A Division of Dominion Enterprises
