David Steele 8820d69574 Use a single file to handle global errors in async archiving. ... The prior behavior on a global error (i.e. not file specific) was to write an individual error file for each WAL file being processed. On retry each of these error files would be removed, and if the error was persistent, they would then be recreated. In a busy environment this could mean tens or hundreds of thousands of files. Another issue was that the error files could not be written until a list of WAL files to process had been generated. This was easy enough for archive-get but archive-push requires more processing and any errors that happened when generating the list would only be reported in the pgBackRest log rather than the PostgreSQL log. Instead write a global.error file that applies to any WAL file that does not have an explicit ok or error file. This reduces churn and allows more errors to be reported directly to PostgreSQL.		2019-03-25 08:12:38 +04:00
..
dtd	Allow if condition in documentation lists and list items.	2019-01-24 16:45:28 +02:00
coding.xml	Add coding standards for String constants.	2018-12-04 11:46:25 -05:00
documentation.xml	Add openssl-devel install to documentation build in 711b3e67.	2019-01-30 22:02:42 +02:00
index.xml	Update introduction to be pithy.	2018-09-19 18:26:12 -04:00
reference.xml	Clarify that encryption is always performed client-side.	2019-01-04 12:25:58 +02:00
release.xml	Use a single file to handle global errors in async archiving.	2019-03-25 08:12:38 +04:00
test.xml	Add admonitions to documentation renderers.	2018-12-30 16:40:20 +02:00
user-guide.xml	Update default documentation version to PostgreSQL 10.	2019-03-01 09:10:14 +02:00