Heikki Linnakangas 72346e102d Document that our code is mostly not async cancellation-safe. ...

We had a hot debate on whether we should try to make our code
cancellation-safe, or just accept that it's not, and make sure that
our Futures are driven to completion. The decision is that we drive
Futures to completion. This documents the decision, and summarizes the
reasoning for that.

Discussion that sparked this:
https://github.com/neondatabase/neon/pull/4198#discussion_r1190209316

2023-05-17 17:29:54 +03:00

..

benches

Rename more zid-like idents (#2480)

2022-09-20 11:06:31 -07:00

scripts

Run regressions tests on both Postgres 14 and 15 (#4192)

2023-05-12 15:28:51 +01:00

src

Document that our code is mostly not async cancellation-safe.

2023-05-17 17:29:54 +03:00

tests

Remove sync postgres_backend, tidy up its split usage.

2023-03-09 20:45:56 +03:00

Cargo.toml

Move PageserverFeedback to utils.

2023-04-28 06:22:13 +04:00