From: | Lonni J Friedman <netllama(at)gmail(dot)com> |
---|---|
To: | maintainers(at)lists(dot)pgrpms(dot)org, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | upgrading from 9.3-beta1 to 9.3-beta2 requires dump & reload? |
Date: | 2013-07-24 20:53:40 |
Message-ID: | CAP=oouEifg1h9tsnfs6dU0EEU0Uifz60cKxJNYBdYCUM212wUg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
I just got around to upgrading from 9.3-beta1 to 9.3-beta2, and was
surprised to see that the server was refusing to start. In the log,
I'm seeing:
2013-07-24 13:41:47 PDT [7083]: [1-1] db=,user= FATAL: database files
are incompatible with server
2013-07-24 13:41:47 PDT [7083]: [2-1] db=,user= DETAIL: The database
cluster was initialized with CATALOG_VERSION_NO 201305061, but the
server was compiled with CATALOG_VERSION_NO 201306121.
2013-07-24 13:41:47 PDT [7083]: [3-1] db=,user= HINT: It looks like
you need to initdb.
I'm using the RPMs from yum.postgresql.org on RHEL6. Is this
expected, intentional behavior? Do I really need to dump & reload to
upgrade between beta releases of 9.3, or is there some more efficient
way?
thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-07-24 20:59:23 | Re: upgrading from 9.3-beta1 to 9.3-beta2 requires dump & reload? |
Previous Message | devonline | 2013-07-24 20:32:15 | Re: Tablespace on Postgrsql |