Re: pg_dumpall reccomendation in release notes - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_dumpall reccomendation in release notes
Date
Msg-id 20140825193631.GD28266@momjian.us
Whole thread Raw
In response to Re: pg_dumpall reccomendation in release notes  (Bruce Momjian <bruce@momjian.us>)
List 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@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Hardening pg_upgrade
Next
From: Heikki Linnakangas
Date:
Subject: Re: psql \watch versus \timing