Re: Versioning policy and pg_upgrade

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Thom Brown <thom(at)linux(dot)com>
Cc: "w^3" <pgsql-www(at)postgresql(dot)org>
Subject: Re: Versioning policy and pg_upgrade
Date: 2010-08-16 12:39:44
Message-ID: AANLkTinFp85iPwLtJS=JSajP5Z0bgUNsKp2w3LFxALFa@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Wed, Aug 11, 2010 at 10:39, Thom Brown <thom(at)linux(dot)com> wrote:
> I noticed that the versioning policy page
> (http://www.postgresql.org/support/versioning) mentions that for
> upgrading between major versions, a dump/reload of the database is
> needed.  Might we want to add a note in there about the use of
> pg_upgrade when upgrading from 8.3+ to 8.4+?  I think some potential
> users might see a dump/reload as a deal-breaker.

Definitely. Care to suggest a wording or even a patch? ;)

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Thom Brown 2010-08-16 12:59:59 Re: Versioning policy and pg_upgrade
Previous Message Magnus Hagander 2010-08-16 08:10:32 Re: [HACKERS] Moderator on Committers?