upgrading from 9.3-beta1 to 9.3-beta2 requires dump & reload?
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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Lonni J Friedman escribi�:
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?
We try to avoid forcing initdb between beta versions, but it's not
guaranteed. You should be able to use pg_upgrade, also.
--
�lvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
Lonni J Friedman escribi�:
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?
We try to avoid forcing initdb between beta versions, but it's not
guaranteed. You should be able to use pg_upgrade, also.
Unfortunately, the RPMs probably won't be very helpful for using
pg_upgrade, since there's no convenient way to get beta1 and beta2
postmaster executables installed at the same time (unless Devrim
foresaw this case and packaged things differently than I did for
Red Hat ;-)).
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Wed, Jul 24, 2013 at 2:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
Lonni J Friedman escribió:
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?We try to avoid forcing initdb between beta versions, but it's not
guaranteed. You should be able to use pg_upgrade, also.Unfortunately, the RPMs probably won't be very helpful for using
pg_upgrade, since there's no convenient way to get beta1 and beta2
postmaster executables installed at the same time (unless Devrim
foresaw this case and packaged things differently than I did for
Red Hat ;-)).
Sounds like I'm out of luck. Thanks anyway.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general