From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Upgrade from postgresql-9.5alpha1 to postgresql-9.5alpha2 (Debian packages) |
Date: | 2015-08-18 11:40:10 |
Message-ID: | CAD21AoDmmxMJtvdwnzjry6CeoxLyrYLe0koJF51AY7tY-27h6g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 18, 2015 at 6:06 PM, Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
> It looks like the catalog version has changed between 9.5alpha1 and
> 9.5alpha2:
>
> FATAL: database files are incompatible with server
> DETAIL: The database cluster was initialized with CATALOG_VERSION_NO 201506282,
> but the server was compiled with CATALOG_VERSION_NO 201507281.
> HINT: It looks like you need to initdb.
>
> Normally, one would use pg_upgradecluster to do the upgrade, but
> pg_upgradecluster assumes that the old and new version are installed in
> parallel. Likewise, the low-level tool pg_upgrade needs the old bindir,
> if I read the man-page correctly, and of course, apt-get upgrade
> overwrites that, since it's just two versions of the same package
> (unlike a major upgrade which is a new package).
>
> So, what's the best way to do the upgrade?
>
> * Copy the bindir before the upgrade (or restore from backup) to a safe
> place and do pg_upgrade?
> * Initdb a new cluster and restore yesterdays backup?
> * Something else?
>
I've not used pg_upgrade at such case, but If you have a enough time
to do upgrading, I will suggest to take backup(pg_dumpall) from
current cluster and then restore it to new cluster.
I think pg_upgrade is basically used at major version upgrading.
Regards,
--
Masahiko Sawada
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Keirse | 2015-08-18 11:47:43 | Re: PostgreSQL conf parameter setting |
Previous Message | Dickson S. Guedes | 2015-08-18 11:30:53 | Re: deletion of the thread posted by me |