Re: Upgrading old server

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Upgrading old server
Date: 2019-09-25 16:00:39
Message-ID: 18538.1569427239@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron <ronljohnsonjr(at)gmail(dot)com> writes:
> On 9/25/19 9:29 AM, Christoph Berg wrote:
>> Re: Ekaterina Amez 2019-09-25 <8818b028-bd2d-412e-d4e3-e29c49ffee17(at)zunibal(dot)com>
>>> We've decided to upgrade our PostgreSQL production servers. First task is
>>> remove an old v7.14 version. It was supposed to be upgraded to a v8.4
>>> server. The server was installed, several databases where released here but
>>> v7.4 was never migrated. The plan is pg_dump this database and psql it to
>>> existing 8.4 server. After this, we'll pg_upgrade.

>> If you doing dump-restore anyway, why not restore into v11 rightaway?

> Since it's recommend to run the newer pg_dump on the older database, I've
> got to wonder if v11 pg_dump can read the v7.4 on-disk structures.

We dropped support for pre-8.0 source servers in pg_dump sometime
recently, though I forget if v11 is affected by that or not.
You could try just dumping with 7.4's pg_dump and seeing if the
output will load into v11 --- ideally it would, but I'd not be
surprised if there are issues that have to be resolved manually.
Or, if you have 8.4's pg_dump at hand, try using that.

7.4 to 11 is a big jump to be doing in one step. There's definitely
something to be said for porting to an intermediate release, just to
break down the work into smaller chunks. But I'd go for halfway between,
which if I counted releases correctly would be about 9.1, not 8.4.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Lewis 2019-09-25 17:44:36 Re: managing primary key conflicts while restoring data to table with existing data
Previous Message Sonam Sharma 2019-09-25 15:55:09 Re: Pg_auto_failover