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
..
Host	Fix static WAL segment size used to determine if archive-push-queue-max has been exceeded.	2018-10-27 20:00:00 +01:00
ConfigEnvTest.pm	Split cfgLoad() into multiple functions to make testing easier.	2018-04-13 16:05:52 -04:00
ExpireEnvTest.pm	Support configurable WAL segment size.	2018-09-25 10:24:42 +01:00
HostEnvTest.pm	Support configurable WAL segment size.	2018-09-25 10:24:42 +01:00
S3EnvTest.pm	Generate global fake cert in containers for testing.	2017-08-08 16:26:44 -04:00