Jeff,
--
If you remove pg_xlogs, I do not expect Postgres to come back!
I think Craig is referring to WAL files , not pg_xlogs. He is still going to take backup of pg_xlogs under $PGDATA when Postgres is still down.
I think there is some misunderstanding here!
On Fri, Dec 6, 2013 at 4:32 PM, Jeff Frost <jeff@xxxxxxxxxxxxx> wrote:
On 12/06/13 13:19, Denish Patel wrote:
> Payal is right. You don't need WAL for Cold backup.
I'm afraid you do.
I just did a test to confirm with 9.2.6:
pg_ctl -D . -m fast stop
rsync . ../data-test -avP
cd ../data-test/pg_xlog
rm -f *
cd ..
pg_ctl -D . start
LOG: could not open file "pg_xlog/00000001000000020000009B" (log file 2,
segment 155): No such file or directory
LOG: invalid primary checkpoint record
LOG: could not open file "pg_xlog/00000001000000020000009B" (log file 2,
segment 155): No such file or directory
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 13141) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
Then, if I copy the WAL files back from the old stopped data dir:
rsync . ../data/pg_xlog/ pg_xlog/ -avP
pg_ctl -D . start
LOG: database system was shut down at 2013-12-06 13:25:13 PST
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
then it happily starts up.
Denish Patel,
OmniTi Computer Consulting Inc.
Database Architect,
http://omniti.com/does/data-management
OmniTi Computer Consulting Inc.
Database Architect,
http://omniti.com/does/data-management
