David Steele 1ad67644da Remove request for S3 object info directly after putting it. ... After a file is copied during backup the size is requested from the storage in case it differs from what was written so that repo-size can be reported accurately. This is useful for situations where compression is being done by the filesystem (e.g. ZFS) and what is stored can differ in size from what was written. In S3 the reported size will always be exactly what was written so there is no need to check the size and doing so immediately can cause problems because the new file might not appear in list commands. This has not been observed on S3 (though it seems to be possible) but it has been reported on the Swift S3 gateway. Add a driver capability to determine if size needs to be called after a file is written and if not then simply use the number of bytes written for repo-size. Reported by Matt Kunkel.		2018-11-30 10:38:02 -05:00
..
dtd	Pre-build containers for any execute elements marked pre.	2018-11-29 14:45:15 -05: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	Remove request for S3 object info directly after putting it.	2018-11-30 10:38:02 -05: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	Pre-build containers for any execute elements marked pre.	2018-11-29 14:45:15 -05:00