Re: Release notes for upgrading

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Release notes for upgrading
Date: 2004-08-11 14:52:03
Message-ID: 1092235923.8616.2057.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2004-08-11 at 01:11, Tom Lane wrote:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> > On Tuesday 10 August 2004 22:57, Christopher Kings-Lynne wrote:
> >> I don't think many users realise they can use the next version's pg_dump
> >> to upgrade. I think it should be put in every release notes!
>
> > Assuming we're not ready to recommend Slony for upgrades, I would second this
> > idea based on my experience of several cases where I *had* to dump a database
> > using the newer pg_dump to get it to upgrade reliably.
>
> This has been standard lore for awhile. Where should we document it
> exactly?
>

Actually it seems it is already mentioned in
http://developer.postgresql.org/docs/postgres/install-upgrading.html and
somewhat inferred in
http://developer.postgresql.org/docs/postgres/migration.html

I'll take a swing at making the language a little stronger. We could
also add it as a mailing list hint. Chris, you have any other ideas
where you would like to see it?

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Pflug 2004-08-11 14:58:49 Re: libpq problem
Previous Message Tom Lane 2004-08-11 14:46:33 Re: will PITR in 8.0 be usable for "hot spare"/"log shipping" type of replication