From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | James Moore <jam(at)memeticsystems(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Problems upgrading from 7.1beta4 to 7.1.0 |
Date: | 2001-06-21 14:56:54 |
Message-ID: | 13357.993135414@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
James Moore <jam(at)memeticsystems(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Volkmar Wieners | 2001-06-21 17:45:41 | Lost oid restoring dump with blobs |
Previous Message | Richard Huxton | 2001-06-21 14:28:29 | Re: Using the extract() function in plpgsql |