Vlad Lazar 0d6d58bd3e pageserver: make heatmap layer download API more cplane friendly (#10957) ...

## Problem

We intend for cplane to use the heatmap layer download API to warm up
timelines after unarchival. It's tricky for them to recurse in the
ancestors,
and the current implementation doesn't work well when unarchiving a
chain
of branches and warming them up.

## Summary of changes

* Add a `recurse` flag to the API. When the flag is set, the operation
recurses into the parent
timeline after the current one is done.
* Be resilient to warming up a chain of unarchived branches. Let's say
we unarchived `B` and `C` from
the `A -> B -> C` branch hierarchy. `B` got unarchived first. We
generated the unarchival heatmaps
and stash them in `A` and `B`. When `C` unarchived, it dropped it's
unarchival heatmap since `A` and `B`
already had one. If `C` needed layers from `A` and `B`, it was out of
luck. Now, when choosing whether
to keep an unarchival heatmap we look at its end LSN. If it's more
inclusive than what we currently have,
keep it.

2025-02-28 10:36:53 +00:00

..

src

pageserver: make heatmap layer download API more cplane friendly (#10957)

2025-02-28 10:36:53 +00:00

Cargo.toml

Remove unnecessary dependencies to synchronous 'postgres' crate (#10938)

2025-02-24 09:40:25 +00:00