David Steele 286f7e5011 Fix static WAL segment size used to determine if archive-push-queue-max has been exceeded. ... This calculation was missed when the WAL segment size was made dynamic in preparation for PostgreSQL 11. Fix the calculation by checking the actual WAL file sizes instead of using an estimate based on WAL segment size. This is more accurate because it takes into account .history and .backup files, which are smaller. Since the calculation is done in the async process the additional processing time should not adversely affect performance. Remove the PG_WAL_SIZE constant and instead use local constants where the old value is still required. This is only the case for some tests and PostgreSQL 8.3 which does not provide a way to get the WAL segment size from pg_control.		2018-10-27 20:00:00 +01:00
..
dtd	Allow containers to be defined in a document.	2018-07-23 07:49:15 -04:00
coding.xml	Storage object improvements.	2018-04-03 12:25:21 -04:00
index.xml	Update introduction to be pithy.	2018-09-19 18:26:12 -04:00
reference.xml	Add checksum delta for incremental backups.	2018-09-19 11:12:45 -04:00
release.xml	Fix static WAL segment size used to determine if archive-push-queue-max has been exceeded.	2018-10-27 20:00:00 +01:00
test.xml	Rename db-* options to pg-* and backup-* options to repo-* to improve consistency.	2018-02-03 18:27:38 -05:00
user-guide.xml	Use command in authorized_hosts to improve SSH security.	2018-09-19 16:41:20 -04:00