32-bit to 64-bit migration screwup

["David Young" <randomfire@xxxxxxxxx>]

All,

 

I was hoping someone can help me fix a big blunder.  I recently bought a new system to replace the old one.  The new system is running 64bit linux and the old one 32bit.  I installed PG 64-bit and tried to bring the old database back up.  Even though I'm running the same version of PG, it is giving me an error when I try to start it back up.  below is the message from pgstartup.log.  It looks like it doesn't recognize the control file anymore.

 

Am I screwed?  I don't have the old system anymore and I didn't do a dump.  I figure if I'm running the same version of PG, the data will come back up correctly.  If someone can help me out of this jam, I would greatly appreciate it.

 

Thanks,

David

 

------------------pgstartup.log---------------

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to UTF8.

fixing permissions on existing directory /var/lib/pgsql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 24MB/153600
creating configuration files ... ok
creating template1 database in /var/lib/pgsql/data/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok

Success. You can now start the database server using:

    /usr/bin/postgres -D /var/lib/pgsql/data
or
    /usr/bin/pg_ctl -D /var/lib/pgsql/data -l logfile start

LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
FATAL:  incorrect checksum in control file
FATAL:  incorrect checksum in control file
FATAL:  incorrect checksum in control file