Christian Schwarz e0b760ad82 walredo: log a few more breadcrumbs on redo failure ...

1. ability to tell whether a replay failure happened in the first or
   later iterations of the request_redo for loop.
2. n_requests, i.e, the  total number of request_redo calls completed
   since the current walredo process start

Possibly these will give us a bit more context about when this is
happening.

This commit is quite ugly and should be reverted or logging
infrastructure in walredo.rs should be generally switched to spans.

2023-10-13 11:53:13 +02:00

..

benches

eliminate WalRedoError type to make {:?} print the innermost backtace

2023-10-13 10:49:14 +02:00

ctl

fix: replace all std::PathBufs with camino::Utf8PathBuf (#5352)

2023-10-04 17:52:23 +03:00

fixtures

walredo: simple tests and bench updates (#3045)

2023-01-16 18:24:45 +02:00

src

walredo: log a few more breadcrumbs on redo failure

2023-10-13 11:53:13 +02:00

Cargo.toml

fix: replace all std::PathBufs with camino::Utf8PathBuf (#5352)

2023-10-04 17:52:23 +03:00