Re: Problem restoring db-dump on Postgres 8.0.4 Power5

From: "Peter Alberer" <peter(dot)alberer(at)wu-wien(dot)ac(dot)at>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Problem restoring db-dump on Postgres 8.0.4 Power5
Date: 2006-01-03 19:52:08
Message-ID: 200601031952.k03JqFbA078389@rumba.wu-wien.ac.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hmmm, i suspect the problem comes from the fact that i did not globally
change gcc to use -m64 nor did I set the enviroment flags (CFLAGS), but
changed the command in the makefile. The configure script did its tests with
the default -m32 and did not define HAVE_LONG_INT_64. Maybe even
INT64_IS_BUSTED is defined for my system...

I tried to run configure with the CFLAGS set to -m64 and it successfully
sets HAVE_LONG_INT_64 in src/include/pg_config.h. So that seems to be my
problem! Btw, after setting the CFLAGS prior to running configure even
ACCEPT_TYPE_ARG3 is defined to be socklen_t.

What do I have to do now? Can I simply continue to run my database instance
(from the existing binary data dictionary) after a recompile/reinstall of
the postgres binaries with a configure script aware of -m64? Or do I have to
fear that the instance is corrupted somehow? Should I do a dump/restore?

Regards, peter

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Qingqing Zhou 2006-01-03 19:54:33 Re: build Postgresql on Solaris 64 bits
Previous Message Joe Conway 2006-01-03 19:13:15 Re: PostgreSQL Arrays and Performance