![]() |
Postgresql Warm standby problem - WAL didn't replay...
Hello all,
I have installed postgres on two machines. Both are similar machines and both are running postgresql 8.3.3. I set up one in archive mode and the other in recovery mode and have set up the copying the WAL archive "push" to the other machine as described here... http://www.postgresql.org/docs/8.3/i...archiving.html I did a test and added a table with some entries...waited about an hour...made sure the WAL archives got pushed over to the other server; then I stopped the primary. I then brought up the warm standby and I waited until the recovery.conf file changed to recovery.done. I logged into the database and the table wasn't there :( I seems that the WAL didn't replay...The database was only as recent as the last pg_dump.... Thoughts/Suggestions/Questions? Thanks, -C |
Solved
Hello all,
After digging through the logs I found out my problem...I appearers that the transaction ID wasn't the same. To solve it; I make a "hot backup" following this http://www.postgresql.org/docs/8.3/i...UP-BASE-BACKUP Then I tar-ed up the data directory as described here... http://www.postgresql.org/docs/8.3/i...ckup-file.html Then I moved the tar-ed datadir and scp-ed it over to the standby database server and untar-ed the tar-ed file in the appropriate location and statred up postgres in "standby mode (continuous recovery)" and I tested the failover mechanism and the database was up to date... Hope this helps! -C |
Congratulations on resolving the issue, and thanks for
updating the thread with the resolution. Cheers, Tink |
All times are GMT -5. The time now is 12:20 PM. |