From 350cd7c47d09754ae21f30f260a86e187054257f Mon Sep 17 00:00:00 2001 From: benoit Date: Thu, 25 Feb 2021 12:08:03 +0100 Subject: [PATCH] Document archive_command failures in more details Document that, if the command was terminated by a signal (other than SIGTERM, which is used as part of a database server shutdown) or an error by the shell with an exit status greater than 125 (such as command not found), then the archiver process will abort and the postmaster will restart it. In such cases, the failure will not be reported in pg_stat_archiver. --- doc/src/sgml/backup.sgml | 8 +++++++- doc/src/sgml/monitoring.sgml | 3 ++- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 3c8aaed0b6..94d5dcbdf0 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -636,7 +636,13 @@ test ! -f /mnt/server/archivedir/00000001000000A900000065 && cp pg_wal/0 PostgreSQL will assume that the file has been successfully archived, and will remove or recycle it. However, a nonzero status tells PostgreSQL that the file was not archived; - it will try again periodically until it succeeds. + it will try again periodically until it succeeds. + An exception is that if the command was terminated by + a signal (other than SIGTERM, which is used as + part of a database server shutdown) or an error by the shell with an exit + status greater than 125 (such as command not found), then the archiver + process will abort and the postmaster will restart it. In such cases, + the failure will not be reported in . diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 3513e127b7..391df3055b 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -3251,7 +3251,8 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i failed_count bigint - Number of failed attempts for archiving WAL files + Number of failed attempts for archiving WAL files (See ) -- 2.25.4