From: Gunnar \"Nick\" Bluth <gunnar.bluth.extern@elster.de>
To: pgsql-docs@postgresql.org
Cc: Gunnar Nick Bluth <gunnar.bluth@pro-open.de>
Subject: Missing important information in backup.sgml
Date: Wed, 16 Nov 2016 11:37:12 +0100
Message-ID: <cb648ec1-5212-60c5-b73a-9572d21b2ae9@elster.de> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Hi,
I ran into this issue (see patch) a few times over the past years, and
tend to forget it again (sigh!). Today I had to clean up a few hundred
GB of unarchived WALs, so I decided to write a patch for the
documentation this time.
inline patch 1: doc/src/sgml/backup.sgml (+0/-0 lines) download inline-1.patchdiff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgmlindex 6eaed1e..460a4f2 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
<productname>PostgreSQL</> will assume that the file has been
successfully archived, and will remove or recycle it. However, a
nonzero
status tells <productname>PostgreSQL</> that the file was not archived;
- it will try again periodically until it succeeds.
+ it will try again periodically until it succeeds. Note that an exit
+ status of 128 or higher will cause the archiver to exit and
<emphasis>not
+ </> try to archive the affected WAL segment anymore. E.g.,
<command>rsync</>
+ tends to return an exit status of 255 when it is unable to resolve a
+ hostname, which - when returned unfiltered - will result in permanent
+ failure to archive the segment, even if the resolving problem is only
+ temporarily.
</para>
<para>
Best regards,
--
Gunnar "Nick" Bluth
DBA ELSTER
Tel: +49 911/991-4665
Mobil: +49 172/8853339
Patches and attachments:download all (3 files, .tar.gz)archiving-doc-exit-status-v1.patch (text/x-patch, 1.0K) downloaddiff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgmlindex 6eaed1e..460a4f2 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
<productname>PostgreSQL</> will assume that the file has been
successfully archived, and will remove or recycle it. However, a nonzero
status tells <productname>PostgreSQL</> that the file was not archived;
- it will try again periodically until it succeeds.+ it will try again periodically until it succeeds. Note that an exit+ status of 128 or higher will cause the archiver to exit and <emphasis>not+ </> try to archive the affected WAL segment anymore. E.g., <command>rsync</>+ tends to return an exit status of 255 when it is unable to resolve a + hostname, which - when returned unfiltered - will result in permanent+ failure to archive the segment, even if the resolving problem is only+ temporarily.
</para>
<para>
signature.asc (application/pgp-signature, 835B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-docs@postgresql.org
Cc: gunnar.bluth.extern@elster.de, gunnar.bluth@pro-open.de
Subject: Re: Missing important information in backup.sgml
In-Reply-To: <cb648ec1-5212-60c5-b73a-9572d21b2ae9@elster.de>
References: <cb648ec1-5212-60c5-b73a-9572d21b2ae9@elster.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox