public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Josh Berkus <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Upgrading doc does not mention pg_restore at all
Date: Sat, 11 Jan 2014 12:47:43 +0100
Message-ID: <CABUevEyZRDb6G5zdp3uPzhYELdT8trZBpTVKbiKqoFe2yDA87Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
On Fri, Jan 10, 2014 at 7:18 PM, Josh Berkus <[email protected]> wrote:
> Folks:
>
> http://www.postgresql.org/docs/9.3/static/upgrading.html
>
> ... no mention of pg_restore of any kind. Is there any reason why
> someone (maybe me) *shouldn't* rewrite this to include pg_restore?
>
I can't see any reason - it definitely should mention it.
Frankly, I think recommending psql to restore is a bad idea ...
>
Yes. And recommending pg_dumpall > sqlfile, but that goes hand in hand with
that.
It also says that the least-downtime way is to use pg_dumpall in a pipe to
psql. That's clearly not correct, since it does not support parallel
restore (or parallel dump).
In short, +1 for you to write a patch that changes that.
It could probably deserve a better descirption of pg_upgrade as well, and
an outline of the differences. Right now we spend the majority of the page
on pg_dump, and then just say "oh, with pg_upgrade it only takes minutes"...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Upgrading doc does not mention pg_restore at all
In-Reply-To: <CABUevEyZRDb6G5zdp3uPzhYELdT8trZBpTVKbiKqoFe2yDA87Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox