Re: upgrading from backend version 811 to 812

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alex Mayrhofer <axelm(at)nona(dot)net>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: upgrading from backend version 811 to 812
Date: 2005-11-08 20:39:24
Message-ID: 8512.1131482364@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alex Mayrhofer <axelm(at)nona(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Matthew T. O'Connor 2005-11-08 20:53:30 Re: autovacuum,8.1, Win
Previous Message Tom Lane 2005-11-08 20:36:40 Re: Setting max_fsm_pages