Re: Problem with documentation of upgrades - Mailing list pgsql-docs

From Bruce Momjian
Subject Re: Problem with documentation of upgrades
Date
Msg-id 201101311823.p0VIN9E25330@momjian.us
Whole thread Raw
In response to Re: Problem with documentation of upgrades  (Bruce Momjian <bruce@momjian.us>)
List pgsql-docs
Bruce Momjian wrote:
> Bruce Momjian wrote:
> > In looking over how upgrades are documented, it seems we talk about
> > dumping/reloading in two place in our documentation:
> >
> >     Chapter 15. Installation from Source Code
> >     15.4. Upgrading
> >     http://developer.postgresql.org/pgdocs/postgres/install-upgrading.html
> >
> > and:
> >
> >     Chapter 24. Backup and Restore
> >     24.4. Migration Between Releases
> >     http://developer.postgresql.org/pgdocs/postgres/migration.html
> >
> > The steps listed also use slightly different syntax, e.g. psql [-d], and
> > we call one "migrating" and the other "upgrading".
> >
> > This really needs a cleanup.  Any suggestions?  I feel the two sections
> > really need to be merged.  Where should the combined section be placed?
>
> I went ahead and merged those two sections and put it in:
>
>     Chapter 17. Server Setup and Operation
>
>     17.6. Upgrading a PostgreSQL Cluster
>         17.6.1. Upgrading Data via pg_dump
>         17.6.2. Other data migration methods
>
> You can view the result here:
>
>     http://momjian.us/expire/pgsql.docs/upgrading.html
>
> There seemed to be continual confusion over whether you need to
> dump/reload, and I think it was because our upgrade instructions were
> duplicative and not complete in both places.  This should solve the
> problem once and for all.

Patch applied.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-docs by date:

Previous
From: Thom Brown
Date:
Subject: Add reference to client_encoding parameter
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade docs