You've already forked pgbackrest
mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2025-11-06 08:49:29 +02:00
Doc fixes for archive-max-mb setting.
This commit is contained in:
@@ -613,7 +613,7 @@ example: archive-async=y
|
||||
|
||||
##### `archive-max-mb` key
|
||||
|
||||
Limits the amount of archive log that will be written locally when `compress-async=y`. After the limit is reached, the following will happen:
|
||||
Limits the amount of archive log that will be written locally when `archive-async=y`. After the limit is reached, the following will happen:
|
||||
|
||||
- PgBackRest will notify Postgres that the archive was succesfully backed up, then DROP IT.
|
||||
- An error will be logged to the console and also to the Postgres log.
|
||||
|
||||
@@ -570,7 +570,7 @@ Run a <id>full</id> backup on the <id>db</id> stanza. <param>--type</param> can
|
||||
|
||||
<!-- CONFIG - ARCHIVE SECTION - ARCHIVE-MAX-MB KEY -->
|
||||
<config-key id="archive-max-mb">
|
||||
<text>Limits the amount of archive log that will be written locally when <setting>compress-async=y</setting>. After the limit is reached, the following will happen:
|
||||
<text>Limits the amount of archive log that will be written locally when <setting>archive-async=y</setting>. After the limit is reached, the following will happen:
|
||||
<ol>
|
||||
<li>PgBackRest will notify Postgres that the archive was succesfully backed up, then DROP IT.</li>
|
||||
<li>An error will be logged to the console and also to the Postgres log.</li>
|
||||
|
||||
Reference in New Issue
Block a user