Content-Type: text/plain; charset=UTF-8
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: General migration question
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Greg Spiegelberg <gspiegelberg@gmail.com>
In-reply-to: <AANLkTin5yrNHgJZ-8LWn8jhT4PZs9Pq=t8_6_pUkUj-i@mail.gmail.com>
References: <AANLkTin5yrNHgJZ-8LWn8jhT4PZs9Pq=t8_6_pUkUj-i@mail.gmail.com>
Date: Tue, 31 Aug 2010 11:07:31 -0400
Message-Id: <1283266911-sup-617@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Greg Spiegelberg's message of mar ago 31 09:04:18 -0400 2010:
> Probably questions best asked on hackers but I figure many are represented here.
> Will there ever be a release where a dump-restore is not necessary?
> Perhaps, at least, minor releases (e.g. 9.0 to 9.1) will not require a
> dump-restore?

9.0 to 9.1 is not a minor release.  9.0.0 to 9.0.1 is a minor release,
and this doesn't require a dump/reload, but it also doesn't have any new
features.  9.0 to 9.1 is just as major as 8.4 to 9.0 is.  (The rule is:
a change in second digit is major release, a change in first digit is
marketing pressure)

You can upgrade in place using pg_upgrade from 8.4 to 9.0 (thus you
don't need dump/reload).  In general, it will be possible to migrate
from one major version to the next with pg_upgrade starting with the
8.4-to-9.0 jump.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support