Christian Schwarz e26ef640c1 pageserver: remove trace_read_requests (#8338) ...

`trace_read_requests` is a per `Tenant`-object option.
But the `handle_pagerequests` loop doesn't know which
`Tenant` object (i.e., which shard) the request is for.

The remaining use of the `Tenant` object is to check `tenant.cancel`.
That check is incorrect [if the pageserver hosts multiple
shards](https://github.com/neondatabase/neon/issues/7427#issuecomment-2220577518).
I'll fix that in a future PR where I completely eliminate the holding
of `Tenant/Timeline` objects across requests.
See [my code RFC](https://github.com/neondatabase/neon/pull/8286) for
the
high level idea.

Note that we can always bring the tracing functionality if we need it.
But since it's actually about logging the `page_service` wire bytes,
it should be a `page_service`-level config option, not per-Tenant.
And for enabling tracing on a single connection, we can implement
a `set pageserver_trace_connection;` option.

2024-07-11 15:17:07 +02:00

..

benches

Remove unused allow's (#6760)

2024-02-14 18:16:05 +00:00

scripts

Upload initdb results to S3 (#5390)

2023-11-23 18:11:52 +00:00

src

pageserver: remove trace_read_requests (#8338)

2024-07-11 15:17:07 +02:00

tests

Remove sync postgres_backend, tidy up its split usage.

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

Cargo.toml

remote_storage config: move handling of empty inline table {} to callers (#8193)

2024-07-02 12:53:08 +02:00