If an anomaly occurs that makes it impossible to extract userlogs, the instance is forcibly stopped.

There are two such cases. One case is that archiving by the archiver process fails. Write an archive_command in postgresql.conf to kill the instance if archiving fails.

The second is a failure of the extraction daemon to write the extraction file. If it fails, the extraction daemon shuts down the instance.

However, such abnormalities may be considered temporary. Therefore, the extraction daemon can specify the number of failures allowed. The default is never to allow. The behavior of the other archiver process is controlled by archive_command. To avoid interfering with the control of the archive_command, the extraction daemon logs a failure to read the archive file at level WARNING, but does not stop.