Skip to content

Thin out materialized skeletons in FossilDB #8495

Open
@fm3

Description

@fm3

Add a script to reduce the FossilDB size by deleting some intermediate materialized skeleton versions. This will be lossless in the sense that they can be reconstructed by applying the update actions on older versions. It will be slower to load these versions then, so we should not overdo it. Definitely keep the oldest and the latest one. Maybe every 100th to 1000th version in between?

Note that since UAV #7917 it is important that the materialized versions of the different collections match, since only update actions are fetched starting at the latest materialized annotation version, regardless of what is present in the skeletons column.

On the other hand, volume actions are only stored and lazily applied since UAV, so anything older might get inconsistent there.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions