pageserver: move toward more efficient IndexPart serialization #4939
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
IndexPart contains two redundant lists of layer names: a set of the names, and then a map of name to metadata.
It also has two places where serialization stuff peeks into the runtime view of the data:
metadata_bytes
, we should just serialize/deserialize it like other serialized data, rather than having to do from_bytes/to_bytes separately.Summary of changes
The IndexPart structure removes
timeline_layers
anddisk_persistent_lsn
.metadata_bytes
becomes justmetadata
. Explicit Serialize and Deserialize implementations map from the serialized structured to the cleaned up IndexPart.The encoding version remains v2, so that existing pageservers are forward compatible to what we write. The
timeline_layers
in serialized version is synthesized from the keys oflayer_metadata
. The next release after deploying this, we can bump the version to 3 and remove the field.Checklist before requesting a review
Checklist before merging