> oops, my mistake the exit code is 0 not 127.
> > My test server's sw/raid array recently died where I kept my PostgreSQL
> > data directory. I
> have
> > both a full dump of the database and a file system back-up of the data
> > directory.
> >
> > I tried to restore my file system back-up first since it is a "fresher"
> > copy. However, I am
> > unable to start postgres. The exit status I get from pg_ctl is "127" but I
> > haven't yet found
> > any
> > documentation relating to it exit-codes. There are no logs file created
> > when I try to start
> up
> > postgresql, so I am a little unsure as to what direction I should take.
> >
> > Should I just make do with the older pg_dump file and re-initdb or is there
> > a way to salvage
> the
> > restored file system back-up.
> >
> > Thanks for any help.
I found the correct log file.
2006-10-10 04:57:45 PDT% LOG: could not open file
"pg_xlog/000000010000000000000055"
(log file 0, segment 85): No such file or
directory
2006-10-10 04:57:45 PDT% LOG: could not open file
"pg_xlog/000000010000000000000055"
(log file 0, segment 85): No such file or
directory
2006-10-10 04:57:45 PDT% LOG: database system was shut down at 2006-09-26
17:11:35 PDT
2006-10-10 04:57:45 PDT% LOG: invalid primary checkpoint record
2006-10-10 04:57:45 PDT% LOG: invalid secondary checkpoint record
2006-10-10 04:57:45 PDT% LOG: logger shutting down
2006-10-10 04:57:45 PDT% LOG: startup process (PID 5953) was terminated by
signal 6
2006-10-10 04:57:45 PDT% PANIC: could not locate a valid checkpoint record
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
