Re: Changes to backup.sgml - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Changes to backup.sgml
Date
Msg-id CA+Tgmob91VkJMkB2wtZfChk5Tp-D1Oba3htLFKB5cH3J_HTM2g@mail.gmail.com
Whole thread Raw
In response to Changes to backup.sgml  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Changes to backup.sgml  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Thu, May 14, 2015 at 12:53 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
> 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.

I agree.  I think this section is just plain weird at this point.
Most people would assume that you can copy or move the database files
when the database server is shut down, but few people would consider
that a usable backup strategy.  I'm not sure exactly how this should
be refactored, but I think something should be done.  Maybe the title
should be something like "Moving or Copying Database Files" instead of
"File System Level Backup", and the content could be adjusted to fit
that theme.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: WALWriteLock contention
Next
From: Tom Lane
Date:
Subject: Re: WALWriteLock contention