Thread
-
Minor disaster after upgrading with cvs.
Christopher Sawtell <csawtell@xtra.co.nz> — 2001-03-15T13:21:14Z
Greetings, I've just - about 4 hours ago upgraded via cvsup and upon restarting PG I was greated by this gem of information 02:10:26 postgres@berty:~ $ ./bin/pg_ctl -o -i start postmaster successfully started 02:10:43 postgres@berty:~ $ FATAL 2: database was initialized with PG_CONTROL_VERSION 0, but the backend was compiled with PG_CONTROL_VERSION 71. looks like you need to initdb. 02:10:50 postgres@berty:~ $ While it is not a total disaster to have to re-create the database tables, it is something I did not forsee. Is there some quick and easy way out of this er situation without having to do an anoyingly non-trivial amount of work? Thanks for everything. -- Sincerely etc., NAME Christopher Sawtell CELL PHONE 021 257 4451 ICQ UIN 45863470 EMAIL csawtell @ xtra . co . nz CNOTES ftp://ftp.funet.fi/pub/languages/C/tutorials/sawtell_C.tar.gz -->> Please refrain from using HTML or WORD attachments in e-mails to me <<-- -
Re: Minor disaster after upgrading with cvs.
Tom Lane <tgl@sss.pgh.pa.us> — 2001-03-15T15:53:57Z
Christopher Sawtell <csawtell@xtra.co.nz> writes: > I've just - about 4 hours ago upgraded via cvsup and upon restarting PG > I was greated by this gem of information > 02:10:26 postgres@berty:~ $ ./bin/pg_ctl -o -i start > postmaster successfully started > 02:10:43 postgres@berty:~ $ FATAL 2: database was initialized with > PG_CONTROL_VERSION 0, > but the backend was compiled with PG_CONTROL_VERSION 71. > looks like you need to initdb. Ah, you have not been paying attention to pghackers (always a good idea when running CVS tip ;-)). You need to run the new contrib utility contrib/pg_resetxlog to update the format of your pg_control and WAL files. regards, tom lane