Commit8c1b6a1

committed

doc: Mention archive_command failure handling on signals

The behavior is similar to restore_command, which was already documentedfor the restore part, but not the archive part.Author: Benoit LobréauReviewed-by: Julien RouhaudDiscussion:https://postgr.es/m/CAPE8EZ7akCzc1hWohA4AcbmKtHh9rcWAB5MStOeZD2+9jC+hLQ@mail.gmail.com

1 parentffd3944 commit8c1b6a1Copy full SHA for 8c1b6a1

File tree

-0

lines changed

-0

lines changed

Lines changed: 9 additions & 0 deletions

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

Comments

(0)