Re: How to upgrade PostgreSQL minor releases without a dump/restore?

From: Kenneth Marshall <ktm(at)rice(dot)edu>
To: Uwe Schroeder <uwe(at)bunspace(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org, gnanam(at)zoniac(dot)com, 'Devrim G?ND?Z' <devrim(at)gunduz(dot)org>
Subject: Re: How to upgrade PostgreSQL minor releases without a dump/restore?
Date: 2011-03-04 14:37:46
Message-ID: 20110304143746.GE8169@aart.is.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Mar 03, 2011 at 07:43:46PM -0800, Uwe Schroeder wrote:
>
> > > ? Did you read the paragraph above?
> > >
> > > Install latest version, and restart postmaster.
> >
> > Installing of latest version as-is will keep overwriting the existing
> > installed directories/files/binaries but not the "/usr/local/pgsql/data/"
> > directory right? Since this is our production server database, am just
> > clarifying this question that came to my mind, before upgrading.
>
> For sake of safety, I'd always make a backup of the data directory. You don't
> need to dump/restore. Just copy the files someplace else and then do the
> update. In case something goes wrong you can always go back to your old
> version and just copy the backup to the data directory.
>
> That's how I do upgrades. Never needed the backup, but better to have one.
>
> Uwe
>
The "Just copy the files someplace else" can take a long, long
time for a large database and you need to have the database off-line
for the copy to be correct. Not really an option in many environments.

Cheers,
Ken

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Heikki Linnakangas 2011-03-04 15:52:29 Re: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum
Previous Message Frank Brendel 2011-03-04 13:58:30 Re: Server doesn't listen error