Re: backup manifests
Robert Haas <robertmhaas@gmail.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Try to avoid compiler warnings in optimized builds.
- 05021a2c0cd2 13.0 landed
-
Fix option related issues in pg_verifybackup.
- 0a89e93bfaa6 13.0 landed
-
Add index term for backup manifest in documentation.
- 4db819ba4039 13.0 landed
-
Code review for backup manifest.
- a2ac73e7be7a 13.0 landed
-
Document the backup manifest file format.
- 149f2ae88ab0 13.0 landed
-
Fix typo in pg_validatebackup documentation.
- c4f82a779d26 13.0 landed
-
Exclude backup_manifest file that existed in database, from BASE_BACKUP.
- 1ec50a81ec0a 13.0 landed
-
Msys2 tweaks for pg_validatebackup corruption test
- c3e4cbaab936 13.0 landed
-
Fix resource management bug with replication=database.
- 3e0d80fd8d3d 13.0 cited
-
Be more careful about time_t vs. pg_time_t in basebackup.c.
- db1531cae009 13.0 cited
-
pg_validatebackup: Fix 'make clean' to remove tmp_check.
- 9f8f881caa0f 13.0 landed
-
pg_validatebackup: Also use perl2host in TAP tests.
- 460314db08e8 13.0 landed
-
Generate backup manifests for base backups, and validate them.
- 0d8c9c1210c4 13.0 landed
-
Add checksum helper functions.
- c12e43a2e0d4 13.0 landed
-
pg_waldump: Add a --quiet option.
- ac44367efbef 13.0 landed
-
Catversion bump for b9b408c48724
- afb5465e0cfc 13.0 cited
-
pg_basebackup: Refactor code for reading COPY and tar data.
- 431ba7bebf13 13.0 landed
-
Use a ResourceOwner to track buffer pins in all cases.
- 3cb646264e8c 12.0 cited
-
Use ARMv8 CRC instructions where available.
- f044d71e331d 11.0 cited
-
Logical replication support for initial data copy
- 7c4f52409a8c 10.0 cited
-
Use Intel SSE 4.2 CRC instructions where available.
- 3dc2d62d0486 9.5.0 cited
-
Switch to CRC-32C in WAL and other places.
- 5028f22f6eb0 9.5.0 cited
-
Remove support for 64-bit CRC.
- 404bc51cde9d 9.5.0 cited
-
Change CRCs in WAL records from 64bit to 32bit for performance reasons.
- 21fda22ec46d 8.1.0 cited
On Thu, Apr 2, 2020 at 1:23 PM Andres Freund <andres@anarazel.de> wrote: > I suspect its possible to control the timing by preventing the > checkpoint at the end of recovery from completing within a relevant > timeframe. I think configuring a large checkpoint_timeout and using a > non-fast base backup ought to do the trick. The state can be advanced by > separately triggering an immediate checkpoint? Or by changing the > checkpoint_timeout? That might make the window fairly wide on normal systems, but I'm not sure about Raspberry Pi BF members or things running CLOBBER_CACHE_ALWAYS/RECURSIVELY. I guess I could try it. > I think it might be worth looking, in a later release, at something like > blake3 for a fast cryptographic checksum. By allowing for instruction > parallelism (by independently checksuming different blocks in data, and > only advancing the "shared" checksum separately) it achieves > considerably higher throughput rates. > > I suspect we should also look at a better non-crypto hash. xxhash or > whatever. Not just for these checksums, but also for in-memory. I have no problem with that. I don't feel that I am well-placed to recommend for or against specific algorithms. Speed is easy to measure, but there's also code stability, the license under which something is released, the quality of the hashes it produces, and the extent to which it is cryptographically secure. I'm not an expert in any of that stuff, but if we get consensus on something it should be easy enough to plug it into this framework. Even changing the default would be no big deal. > FWIW, the only check I'd really like to see in this release is the > crosscheck with the files length and the actually read data (to be able > to disagnose FS issues). Not sure I understand this comment. Isn't that a subset of what the patch already does? Are you asking for something to be changed? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company