Thread: different catalogue version numbers?

Hi,

I suspect this is actually a Debian question, but I thought someone here
could point me in the right direction in interpreting an error message.  I
was working with one of the betas of Postgresql 7, and thought it would be
nice to catch some of the bugfixes.  So, I installed the release version
(provided as a Debian package).  Now, I can't get to my data:

$ 000602.17:24:31.191  [5066] DEBUG:  Data Base System is starting up at Fri
Jun  2 17:24:31 2000
000602.17:24:31.217  [5066] FATAL 2:  database was initialized with
CATALOG_VERSION_NO 200003141,
        but the backend was compiled with CATALOG_VERSION_NO 200005041.
        looks like you need to initdb.
000602.17:24:31.217  [5066] FATAL 2:  database was initialized with
CATALOG_VERSION_NO 200003141,
        but the backend was compiled with CATALOG_VERSION_NO 200005041.
        looks like you need to initdb.
Startup failed - abort

Do I need to restore the dumped data?  I can do that, but mostly I'm curious
about what happened.

A

--
Andrew Sullivan                                      Computer Services
<sullivana@bpl.on.ca>                        Burlington Public Library
+1 905 639 3611 x158                                   2331 New Street
                                   Burlington, Ontario, Canada L7R 1J4

Andrew Sullivan <sullivana@bpl.on.ca> writes:
> 000602.17:24:31.217  [5066] FATAL 2:  database was initialized with
> CATALOG_VERSION_NO 200003141,
>         but the backend was compiled with CATALOG_VERSION_NO 200005041.
>         looks like you need to initdb.

Yup, that's a check that was added in hopes of improving over the old
crash-and-burn behavior when you tried to run a backend with an
incompatible database...

            regards, tom lane