From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Problem with documentation of upgrades |
Date: | 2011-01-28 20:43:59 |
Message-ID: | 201101282043.p0SKhxO05810@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-01-29 18:04:45 | Re: title capitalization |
Previous Message | Tom Lane | 2011-01-28 17:11:51 | Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd |