database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-28 18:48:04 +03:00
Code Activity

doc: Improve some markups and some wording around archiving modules

Browse Source 
This commit adds or fixes markups used in a couple of places in the docs
(for <command>, <systemitem> and <literal>).  While on it, this
clarifies some of the documentation added recently for archiving modules
with archive_command, that would still be used as default choice if no
external module is defined (though an archive module could as well use
an archive_command).

Author: Maxim Yablokov
Discussion: https://postgr.es/m/b47ec4e8-6f6a-2aba-038e-d5db150b245e@postgrespro.ru
Backpatch-through: 15
This commit is contained in:
Michael Paquier
2022-08-19 10:00:12 +09:00
parent 662ba729a6
commit 31e121d4f7
7 changed files with 31 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/basebackup-to-shell.sgml
View File

@@ -10,11 +10,11 @@
<para>
<filename>basebackup_to_shell</filename> adds a custom basebackup target
called <literal>shell</literal>. This makes it possible to run
<literal>pg_basebackup --target=shell</literal> or, depending on how this
<command>pg_basebackup --target=shell</command> or, depending on how this
module is configured,
<literal>pg_basebackup --target=shell:DETAIL_STRING</literal>, and cause
a server command chosen by the server administrator to be executed for
each tar archive generated by the backup process. The command will receive
<command>pg_basebackup --target=shell:<replaceable>DETAIL_STRING</replaceable></command>,
and cause a server command chosen by the server administrator to be executed
for each tar archive generated by the backup process. The command will receive
the contents of the archive via standard input.
</para>