From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Michael Wuttke <m(dot)wuttke(at)elektropost(dot)org> |
Cc: | pgsql-pkg-debian(at)postgresql(dot)org |
Subject: | Re: howto upgrade from 8.4 to 9.2 without the remove & install of postgresql |
Date: | 2012-12-28 12:09:08 |
Message-ID: | 20121228120907.GC26096@msgid.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
Re: Michael Wuttke 2012-12-23 <50D6BE18(dot)6050103(at)elektropost(dot)org>
> But the upgrade from the debian pgdg package (postgresql-8.4.15-1.pgdg)
> to the debian pgdg package (postgresql-9.2.2-1.pgdg) unfortunately does
> not work, as I had expected.
>
> I had two postgresql installations, one postgresql 8.4 installation
> listening on port 5432 and one postgresql 9.2 installation listening on
> port 5433. Both postgresql installations could be started and stopped
> with the /etc/intit-script. But the installations on postgresql-8.4 were
> unavailable.
I don't really get the problem description. Do you mean you had 2
installations before doing the change, or just after installing 9.2?
It is expected that installing postgresql-9.2 will create a new
cluster on port 5433 (or generally N+1). If you want your old data to
be migrated, drop the new (empty) cluster, and use pg_upgradecluster
on the 8.4 one.
(Btw, nothing of this is PGDG-specific, it works just like that if you
are upgrading to a new PostgreSQL version in pure Debian.)
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2013-01-02 11:07:30 | Re: "ulimit -n" in postgresql/pgbouncer init scripts. |
Previous Message | Christoph Berg | 2012-12-28 11:56:54 | Re: "ulimit -n" in postgresql/pgbouncer init scripts. |