Re: backup.sgml patch that adds information on custom format backups

From: Ivan Lezhnjov IV <iliv(at)commandprompt(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: backup.sgml patch that adds information on custom format backups
Date: 2013-02-27 11:11:40
Message-ID: 57DD6920-9CEB-4629-B681-3CBDE4AAF8F8@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alright gentlemen here we go, take two.

backup.sgml-cmd-v002.patch addresses your feedback and offers a better worded statements that avoid implying that some features are being deprecated when it isn't the case. We also spent some more time polishing other details, like making adjustments to the tone of the text so that it sounds like a manual, not a blog post, more importantly, making it clear that superuser privileges are not always required to perform a successful backup in practice as long as the role used to make the backup has sufficient read privileges on all of the objects a user is interested in. We also mention and show examples of usage for pigz alongside with gzip, and probably something else too :P Please, see the diff file attached to this message for complete and detailed log of the changes.

Attachment Content-Type Size
backup.sgml-cmd-v002.patch application/octet-stream 8.0 KB
unknown_filename text/plain 1 byte

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2013-02-27 11:33:44 Re: "COPY foo FROM STDOUT" and ecpg
Previous Message Andres Freund 2013-02-27 10:01:06 Re: pg_xlogdump compiler warning