Vlad Lazar 62c0152e6b pageserver: shut down compute connections at libpq level (#12642) ...

## Problem

Previously, if a get page failure was cause by timeline shutdown, the
pageserver would attempt to tear down the connection gracefully:
`shutdown(SHUT_WR)` followed by `close()`.

This triggers a code path on the compute where it has to tell apart
between an idle connection and a closed one. That code is bug prone, so
we can just side-step the issue by shutting down the connection via a
libpq error message.

This surfaced as instability in test_shard_resolve_during_split_abort.
It's a new test, but the issue existed for ages.

## Summary of Changes

Send a libpq error message instead of doing graceful TCP connection
shutdown.

Closes LKB-648

2025-07-17 21:03:55 +00:00

..

src

pageserver: shut down compute connections at libpq level (#12642)

2025-07-17 21:03:55 +00:00

tests

apply clippy fixes for 1.88.0 beta (#12331)

2025-06-24 10:12:42 +00:00

Cargo.toml

Remove unnecessary dependencies (#9000)

2024-09-17 17:55:45 +03:00