| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade docs |
| Date: | 2011-01-31 20:22:58 |
| Message-ID: | 201101312022.p0VKMw426784@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Bruce Momjian wrote:
> I have created the attached patch which rewords the mention of
> pg_upgrade in the docs. I think it is clearer and more concise. Should
> we mention that people should have a recent pg_dump? If so, that should
> be in the pg_upgrade man page, not here.
Applied attached patch that mentions pg_upgrade in a less risk-warning
way, and incorporate Robert Haas's ideas (mention storage format
changes) into pg_upgrade docs.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| Attachment | Content-Type | Size |
|---|---|---|
| /rtmp/pg_upgrade.diff | text/x-diff | 2.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Itagaki Takahiro | 2011-02-01 05:31:02 | Re: [HACKERS] Add reference to client_encoding parameter |
| Previous Message | Bruce Momjian | 2011-01-31 18:23:09 | Re: Problem with documentation of upgrades |