Re: Upgrading from 7.1.3 to 7.2.3

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Andrew Sullivan <andrew(at)libertyrms(dot)info>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Upgrading from 7.1.3 to 7.2.3
Date: 2002-11-12 17:11:14
Message-ID: Pine.LNX.4.33.0211121008310.24725-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I ALWAYS do the first migration onto a test box first. I.e. I pg_dumpall
on the old machine, ftp the file into the test server with a fresh build
of the new postgresql and do a pg_restore on that box to make sure the
upgrade will work.

It's not uncommon for things like sequences, rules, triggers, user defined
functions etc... to have some issues with an upgrade.

I've often found that using the pg_dump from the newer version of
postgresql against the older server is an answer to a lot of these
problems, and if I remember correctly, that was the fix for a few upgrade
issues when going to 7.2.x.

On Tue, 12 Nov 2002, Andrew Sullivan wrote:

> On Sun, Nov 10, 2002 at 02:59:58PM -0800, Aurangzeb M. Agha wrote:
> >
> > BTW, the first thing I did was make two copies of DB/data.
>
> While you were shut down, right? Because if not, your copies may be
> useless.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message scott.marlowe 2002-11-12 17:19:59 Re: how do i insert a default value?
Previous Message scott.marlowe 2002-11-12 17:07:42 Re: RE : Stability problems