Christian Schwarz 2bc2fd9cfd fixup(#7160 / tokio_epoll_uring_ext): double-panic caused by info! in thread-local's drop() (#7164) ...

Manual testing of the changes in #7160 revealed that, if the
thread-local destructor ever runs (it apparently doesn't in our test
suite runs, otherwise #7160 would not have auto-merged), we can
encounter an `abort()` due to a double-panic in the tracing code.

This github comment here contains the stack trace:
https://github.com/neondatabase/neon/pull/7160#issuecomment-2003778176

This PR reverts #7160 and uses a atomic counter to identify the
thread-local in log messages, instead of the memory address of the
thread local, which may be re-used.

2024-03-18 16:12:01 +01:00

..

benches

bench_walredo: use tokio multi-threaded runtime (#6743)

2024-02-16 16:31:54 +01:00

client

pageserver, controller: improve secondary download APIs for large shards (#7131)

2024-03-15 19:45:58 +00:00

compaction

Minor improvements to tiered compaction (#7020)

2024-03-05 16:26:51 +01:00

ctl

pageserver: optimise disk io for vectored get (#6780)

2024-02-28 12:06:00 +00:00

pagebench

tokio-epoll-uring: use it for on-demand downloads (#6992)

2024-03-15 18:57:05 +00:00

src

fixup(#7160 / tokio_epoll_uring_ext): double-panic caused by info! in thread-local's drop() (#7164)

2024-03-18 16:12:01 +01:00

test_data

Add walingest test (#5892)

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

Cargo.toml

build: make procfs linux only dependency (#7156)

2024-03-18 09:28:45 +00:00