database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

doc: Mention archive_command failure handling on signals

Browse Source 
The behavior is similar to restore_command, which was already documented
for the restore part, but not the archive part.

Author: Benoit Lobréau
Reviewed-by: Julien Rouhaud
Discussion: https://postgr.es/m/CAPE8EZ7akCzc1hWohA4AcbmKtHh9rcWAB5MStOeZD2+9jC+hLQ@mail.gmail.com
This commit is contained in:
Michael Paquier
2021-03-02 10:25:47 +09:00
parent ffd3944ab9
commit 8c1b6a186d
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/backup.sgml
View File

@ -639,6 +639,15 @@ test ! -f /mnt/server/archivedir/00000001000000A900000065 && cp pg_wal/0
it will try again periodically until it succeeds.
</para>
<para>
When the archive command is terminated by a signal (other than
<systemitem>SIGTERM</systemitem> that is used as part of a server
shutdown) or an error by the shell with an exit status greater than
125 (such as command not found), the archiver process aborts and gets
restarted by the postmaster. In such cases, the failure is
not reported in <xref linkend="pg-stat-archiver-view"/>.
</para>
<para>
The archive command should generally be designed to refuse to overwrite
any pre-existing archive file. This is an important safety feature to