On Sat, May 2, 2009 at 7:14 PM, Arun Khan <[email protected]> wrote:
> I am testing the migrated data by providing a link file "data" pointing
> to either the bare db created by initdb during install (data.install)
> or the data.amd64 dir migrated from the old machine.
>
> When "data" is linked to data.install, pg starts and the logfiles are in
> data/pg_log.
>
> When "data" is pointing to data.amd64 then pg start hangs for ~ 2 mins
> and then displays "failed" there is no log file in data/pg_log
In your case, the pg_ctl start command is failing. You should modify
the init.d script to log the output of this command somewhere instead
of /dev/null. You should add a line similar to the one following:
su - $PGUSER -c "$DAEMON -D '$PGDATA' &" >>/var/log/pgsql.log 2>&1
You did not specify, but sounds like the source machine is a 64 bit
one and destination is a 32 bit machine? If yes, i'm not sure if it is
going to work this way. AFAIK, the data directory may be different for
different architectures. You should dig deep to find out what's
holding you back.
If that does not help, you may look out for options to migrate the
data directory from AMD -> INTEL. If that does not help, you may also
check if there's a tool to generate sql commands out of data
directory. If yes, you can use the tool to create the sql dump file
and restore it into the new data directory.
Good luck!
--
Regards,
Bhuvaneswaran A
www.livecipher.com
GPG: 0x7A13E5B0
_______________________________________________
To unsubscribe, email [email protected] with
"unsubscribe <password> <address>"
in the subject or body of the message.
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
