Re: backup manifests
Bruce Momjian <bruce@momjian.us>
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 Tue, Jan 14, 2020 at 12:53:04PM -0500, Tom Lane wrote: > Also worth noting is that we have a seriously bad track record about > choosing external packages to depend on. The regex code has no upstream > maintainer anymore (well, the Tcl guys seem to think that *we* are > upstream for that now), and snowball is next door to moribund. > With C not being a particularly hip language to develop in anymore, > it wouldn't surprise me in the least for any C-code JSON parser > we might pick to go dead pretty soon. > > Between that problem and the likelihood that we'd need to make > significant code changes anyway to meet our own coding style etc > expectations, I think really we'd have to assume that we're going > to fork and maintain our own copy of any code we pick. > > Now, if it's a small enough chunk of code (and really, how complex > is JSON parsing anyway) maybe that doesn't matter. But I tend to > agree with Robert's position that it's a big ask for this patch > to introduce a frontend JSON parser. I know we have talked about our experience in maintaining external code: * TCL regex * Snowball * Timezone handling However, the regex code is complex, and the Snowball and timezone code is improved as they add new languages and time zones. I don't see JSON parsing as complex or likely to change much, so it might be acceptable to include it in our frontend code. As far as using tab-delimited data, I know this usage was compared to postgresql.conf and pg_hba.conf, which don't change much. However, those files are not usually written, and do not contain user data, while the backup file might contain user-specified paths if they are not just relative to the PGDATA directory, and that would make escaping a requirement. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +