Thread: fatal error - different CATALOG_VERSION_NO

i just cvs update and recompiled -current. upon starting up i get:

<cut>
# su pgsql
$ pg_ctl start -w -D /var/pgsql/data&
$ Waiting for postmaster to start up...FATAL 2:  database was initialized
with CATALOG_VERSION_NO
 200012280,
        but the backend was compiled with CATALOG_VERSION_NO 200101061.
        looks like you need to initdb.
...............................
</cut>


do i have to follow the upgrade procedures? i have some important data
that i don't want to lose or mess up on.

Thomas T. Thai writes:

> $ Waiting for postmaster to start up...FATAL 2:  database was initialized
> with CATALOG_VERSION_NO
>  200012280,
>         but the backend was compiled with CATALOG_VERSION_NO 200101061.
>         looks like you need to initdb.

> do i have to follow the upgrade procedures?

Yes

--
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/

>> $ Waiting for postmaster to start up...FATAL 2:  database was initialized
>> with CATALOG_VERSION_NO
>> 200012280,
>> but the backend was compiled with CATALOG_VERSION_NO 200101061.
>> looks like you need to initdb.

>> do i have to follow the upgrade procedures?

> Yes

If you're trying to store useful data in a CVS-tip installation,
it's a good idea to pay close attention to the CVS logs, particularly
http://www.postgresql.org/cgi/cvsweb.cgi/pgsql/src/include/catalog/catversion.h
which will keep you posted on initdb-forcing changes.

Or to be really safe, always do a backup before updating.

            regards, tom lane