Thread: upgrading from backend version 811 to 812
Hi, is there any way to upgrade an 811 backend version cluster to the current 812 version? Any "don't try at home"-type tricks? I'm willing to risk cluster corruption, because this is just a test database (but it is rather large). thanks, alex
811? 812? We don't have anything close to those version numbers... If you're upgrading to 8.1 you need to dump/reload, unless you're comming from a recent RC or beta. You *might* be able to get away with a simple drop-in upgrade in that case. On Tue, Nov 08, 2005 at 08:25:31PM +0100, Alex Mayrhofer wrote: > Hi, > > is there any way to upgrade an 811 backend version cluster to the current > 812 version? Any "don't try at home"-type tricks? > > I'm willing to risk cluster corruption, because this is just a test > database (but it is rather large). > > thanks, > > alex > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Jim C. Nasby wrote: > 811? 812? We don't have anything close to those version numbers... I'm well aware that PostgreSQL itself is currently at 8.1.0 - however, i'm upgrading from 8.1beta2, and it seems to me that the backend version was modified between those two versions - "811" and "812" seem to be backend version identifiers which are reported when i'm trying to start the 8.1.0 postmaster on the 8.1beta2 cluster: FATAL: database files are incompatible with server DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 811, but the server was compiled with PG_CONTROL_VERSION 812. HINT: It looks like you need to initdb. > If you're upgrading to 8.1 you need to dump/reload, unless you're > comming from a recent RC or beta. You *might* be able to get away with a > simple drop-in upgrade in that case. tried that - does not work. That's why i'm asking... thanks, Alex
Alex Mayrhofer <axelm@nona.net> writes:
> Jim C. Nasby wrote:
>> 811? 812? We don't have anything close to those version numbers...
> I'm well aware that PostgreSQL itself is currently at 8.1.0 - however, i'm
> upgrading from 8.1beta2, and it seems to me that the backend version was
> modified between those two versions - "811" and "812" seem to be backend
> version identifiers which are reported when i'm trying to start the 8.1.0
> postmaster on the 8.1beta2 cluster:
> FATAL: database files are incompatible with server
> DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 811,
> but the server was compiled with PG_CONTROL_VERSION 812.
Those are internal version numbers that no one normally ever sees, and
certainly no one thinks about. You shouldn't try to outsmart us by
referring to versions in other than the standard terms.
The short answer, though, is that if the postmaster won't restart then
you need a dump with the old code and reload with the new.
regards, tom lane
Tom Lane wrote: >> DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 811, >> but the server was compiled with PG_CONTROL_VERSION 812. > > Those are internal version numbers that no one normally ever sees, and > certainly no one thinks about. You shouldn't try to outsmart us by > referring to versions in other than the standard terms. sorry, that was of course unintentional. I regret that i haven't been more precise in my first message. > The short answer, though, is that if the postmaster won't restart then > you need a dump with the old code and reload with the new. ok, thanks. cheers alex