Обсуждение: Problems upgrading from 7.1beta4 to 7.1.0

Yesterday I attempted to upgrade a system running 7.1 beta4 RPMS that I
built from the SRPM to 7.1.0 RPMS built from the SRPMS.  I assumed that
since the version number difference was minor I wouldn't have a problem
upgrading the server but when I tried to start it up it complained about
PG_CONTROL being set to 0 when the backend was set to 71. I created a
new data directory and copied global/pg_control to my old data
directory. When I tried starting it again it says

DEBUG:  open(logfile 0 seg 2) failed: No such file or directory
DEBUG:  Invalid primary checkPoint record
DEBUG:  open(logfile 0 seg 2) failed: No such file or directory
DEBUG:  Invalid secondary checkPoint record
FATAL 2:  Unable to locate a valid CheckPoint record
/usr/bin/postmaster: Startup proc 16406 exited with status 512 - abort

Any ideas?

--

-James

James Moore <jam@memeticsystems.com> writes:
> Yesterday I attempted to upgrade a system running 7.1 beta4 RPMS that I
> built from the SRPM to 7.1.0 RPMS built from the SRPMS.  I assumed that
> since the version number difference was minor I wouldn't have a
> problem

If you're going to run beta releases then it behooves you to pay more
attention to the mailing lists... see
http://www.ca.postgresql.org/mhonarc/pgsql-announce/2001-03/msg00003.html

> upgrading the server but when I tried to start it up it complained about
> PG_CONTROL being set to 0 when the backend was set to 71. I created a
> new data directory and copied global/pg_control to my old data
> directory.

The intended way to update early beta releases to 7.1 final is to run
contrib/pg_resetxlog.  I am not sure if this will still work for you
(it'd have been a lot better if you'd asked *before* zapping your
control file), but try it.

            regards, tom lane