backup.sgml-cmd-v003.patch
От | Ivan Lezhnjov IV |
---|---|
Тема | backup.sgml-cmd-v003.patch |
Дата | |
Msg-id | B1DC07C6-38FE-4B07-8246-245C34697403@commandprompt.com обсуждение исходный текст |
Ответы |
Re: backup.sgml-cmd-v003.patch
Re: backup.sgml-cmd-v003.patch |
Список | pgsql-hackers |
Hello, I'd like to properly resubmit this patch, under a new version now. Somehow this effort fell by the wayside. Project: postgresql Patch filename: backup.sgml-cmd-v003.patch The third version of this patch takes into consideration feedback received after original submission (it can be read startingfrom this message http://www.postgresql.org/message-id/CA+Tgmoaq-9D_mst113TdW=Ar8mpgBc+x6T61AzK3eMhww9gRcQ@mail.gmail.com) Essentially, it addresses the points that were raised in community feedback and offers better worded statements that avoidimplying that some features are being deprecated when it isn't the case. We also spent some more time polishing otherdetails, like making adjustments to the tone of the text so that it sounds more like a manual, and less like a blogpost. More importantly, this chapter now makes it clear that superuser privileges are not always required to performa successful backup because in practice as long as the role used to make a backup has sufficient read privileges onall of the objects a user is interested in it's going to work just fine. We also mention and show examples of usage forpg_restore and pigz alongside with gzip, and probably something else too. Please, see the patch file (git diff) attached to this message for complete and detailed log of the changes. An html version of the document generated from this patch is included as a preview for your convenience also. It is meant for application, and is against master branch. The patch does pass 'make check' and 'make html' successfully. Ivan
Вложения
В списке pgsql-hackers по дате отправления: