Re: pg_dumpall reccomendation in release notes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dumpall reccomendation in release notes
Date: 2014-08-25 19:36:31
Message-ID: 20140825193631.GD28266@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 21, 2014 at 12:18:46PM -0400, Bruce Momjian wrote:
> I have developed the attached patch to address the issues raised above:
>
> o non-text output of pg_dump is mentioned
> o mentions of using OID for keys is removed
> o the necessity of pg_dumpall --globals-only is mentioned
> o using pg_dump parallel mode rather than pg_dumpall for upgrades is mentioned
> o pg_upgrade is mentioned more prominently for upgrades
> o replication upgrades are in their own section
>
> I don't think we want to mention pg_upgrade as the _primary_
> major-version upgrade method. While the pg_dump upgrade section is
> long, it is mostly about starting/stoping the server, moving
> directories, etc, the same things you have to do for pg_upgrade, so I
> just mentioned that int the pg_upgrade section. Other ideas?
>
> I plan to apply this to head and 9.4.

Updated patch attached and applied.

Any other suggestions? Please let me know.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

Attachment Content-Type Size
upgrade.diff text/x-diff 10.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-08-25 19:45:50 Re: Set new system identifier using pg_resetxlog
Previous Message Bruce Momjian 2014-08-25 19:29:30 Re: Hardening pg_upgrade