Dmitry Rodionov d53f9ab3eb delete timelines from s3 (#4384) ...

Delete data from s3 when timeline deletion is requested

## Summary of changes

UploadQueue is altered to support scheduling of delete operations in
stopped state. This looks weird, and I'm thinking whether there are
better options/refactorings for upload client to make it look better.

Probably can be part of https://github.com/neondatabase/neon/issues/4378

Deletion is implemented directly in existing endpoint because changes are not
that significant. If we want more safety we can separate those or create
feature flag for new behavior.

resolves [#4193](https://github.com/neondatabase/neon/issues/4193)

---------

Co-authored-by: Joonas Koivunen <joonas@neon.tech>

2023-06-08 15:01:22 +03:00

..

benchmarking.yml

Nightly Benchmarks: add neonvm to pgbench-compare (#4225)

2023-05-16 12:46:28 +01:00

build_and_test.yml

delete timelines from s3 (#4384)

2023-06-08 15:01:22 +03:00

neon_extra_builds.yml

GitHub Workflows: use ref_name instead of ref

2023-04-12 15:22:18 +01:00

pg_clients.yml

GitHub Workflows: use ref_name instead of ref

2023-04-12 15:22:18 +01:00

release.yml

Revert "Add neondatabase/release team as a default reviewers for storage"

2023-03-27 14:10:18 +04:00