Arpad Müller 215cdd18c4 Make initdb upload retries cancellable and seek to beginning (#6147) ...

* initdb uploads had no cancellation token, which means that when we
were stuck in upload retries, we wouldn't be able to delete the
timeline. in general, the combination of retrying forever and not having
cancellation tokens is quite dangerous.
* initdb uploads wouldn't rewind the file. this wasn't discovered in the
purposefully unreliable test-s3 in pytest because those fail on the
first byte always, not somewhere during the connection. we'd be getting
errors from the AWS sdk that the file was at an unexpected end.

slack thread: https://neondb.slack.com/archives/C033RQ5SPDH/p1702632247784079

2023-12-15 12:11:25 +00:00

..

benches

pageserver: refactor TenantId to TenantShardId in Tenant & Timeline (#5957)

2023-11-29 14:52:35 +00:00

ctl

pagectl: add subcommand to rewrite layer file summary (#5933)

2023-11-30 11:34:30 +00:00

src

Make initdb upload retries cancellable and seek to beginning (#6147)

2023-12-15 12:11:25 +00:00

test_data

Add walingest test (#5892)

2023-11-28 12:50:53 -05:00

Cargo.toml

pageserver: heatmap uploads (#6050)

2023-12-14 13:09:24 +00:00