db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-01-30 05:39:12 +02:00
Code Issues Releases Activity

Fix incorrect command in reference documentation.

Browse Source 
Also update process to command to be more consistent with the surrounding text.
This commit is contained in:
Magnus Hagander 2020-05-12 19:13:04 +02:00 committed by GitHub
parent 33cbdb78fd
commit b8a5c3ac6f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/xml/reference.xml
View File

@ -229,7 +229,7 @@
The asynchronous <cmd>archive-push</cmd> command writes acknowledgements into the spool path when it has successfully stored WAL in the archive (and errors on failure) so the foreground process can quickly notify <postgres/>. Acknowledgement files are very small (zero on success and a few hundred bytes on error).
The asynchronous <cmd>archive-push</cmd> process queues WAL in the spool path so it can be provided very quickly when <postgres/> requests it. Moving files to <postgres/> is most efficient when the spool path is on the same filesystem as <path>pg_xlog</path>/<path>pg_wal</path>.
The asynchronous <cmd>archive-get</cmd> command queues WAL in the spool path so it can be provided very quickly when <postgres/> requests it. Moving files to <postgres/> is most efficient when the spool path is on the same filesystem as <path>pg_xlog</path>/<path>pg_wal</path>.
The data stored in the spool path is not strictly temporary since it can and should survive a reboot. However, loss of the data in the spool path is not a problem. <backrest/> will simply recheck each WAL segment to ensure it is safely archived for <cmd>archive-push</cmd> and rebuild the queue for <cmd>archive-get</cmd>.

2
src/config/define.auto.c
View File

@ -4543,7 +4543,7 @@ static ConfigDefineOptionData configDefineOptionData[] = CFGDEFDATA_OPTION_LIST
"in the archive (and errors on failure) so the foreground process can quickly notify PostgreSQL. Acknowledgement "
"files are very small (zero on success and a few hundred bytes on error).\n"
"\n"
"The asynchronous archive-push process queues WAL in the spool path so it can be provided very quickly when PostgreSQL "
"The asynchronous archive-get command queues WAL in the spool path so it can be provided very quickly when PostgreSQL "
"requests it. Moving files to PostgreSQL is most efficient when the spool path is on the same filesystem as "
"pg_xlog/pg_wal.\n"
"\n"