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
referrin
Alex Mayrhofer <[EMAIL PROTECTED]> 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
> modifie
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
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 Mayrhof
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 broadca
