From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Migration page is out of date |
Date: | 2011-09-06 16:40:54 |
Message-ID: | 201109061640.p86Ges103842@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Robert Haas wrote:
> On Tue, Mar 22, 2011 at 12:56 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> > http://www.postgresql.org/docs/9.0/static/migration.html
> >
> > This page:
> >
> > a) has insufficient coverage of pg_upgrade
> > b) ignores parallel pg_restore
> > c) piping pg_dump is by no means always the fastest method
> >
> > I'll write up a new version later, just wanted to put this note on the
> > ML so that somebody would bug me before the end of 9.1 beta.
>
> Hey, you!
I am not sure if you were aware that I re-did the upgrade section of the
docs to clearly mention pg_upgrade and other issues:
http://www.postgresql.org/docs/9.1/static/upgrading.html
I am not sure how to mention parallel pg_restore when pg_dumpall can't
be used in parallel restore mode.
Any suggested changes?
--
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-09-07 02:54:39 | Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers |
Previous Message | Tom Lane | 2011-09-06 15:52:32 | Re: about value storage |