Changes to backup.sgml - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Changes to backup.sgml
Date
Msg-id 5554D2ED.2090602@commandprompt.com
Whole thread Raw
Responses Re: Changes to backup.sgml  (Bruce Momjian <bruce@momjian.us>)
Re: Changes to backup.sgml  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
-hackers,

After my brain flatulence last week on backups, I decided to read the 
docs again. There are some improvements that I would like to make and 
wanted some feedback:

1. File System Level Backup

The section should be a note within the larger document. It is largely a 
legacy section from before 8.3.

2. Rework the paragraph about consistent snapshots into its own section

3. Push the rsync paragraph (and edit where appropriate) within the 
continuous archiving section.
3a. Add information about robocopy (windows rsync)

4. Move continuous archiving up above everything except pg_dump. Perhaps 
change time to Online Backup.
4a. I want to do some general rewording, there are some places where 
the documentation is not clear. I can just do this and then let the 
reviewers have their say.

JD


-- 
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: trust authentication behavior
Next
From: Andrew Dunstan
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file