Erik Grinaker 6b19867410 safekeeper: don't flush control file on WAL ingest path (#9698) ...

## Problem

The control file is flushed on the WAL ingest path when the commit LSN
advances by one segment, to bound the amount of recovery work in case of
a crash. This involves 3 additional fsyncs, which can have a significant
impact on WAL ingest throughput. This is to some extent mitigated by
`AppendResponse` not being emitted on segment bound flushes, since this
will prevent commit LSN advancement, which will be addressed separately.

## Summary of changes

Don't flush the control file on the WAL ingest path at all. Instead,
leave that responsibility to the timeline manager, but ask it to flush
eagerly if the control file lags the in-memory commit LSN by more than
one segment. This should not cause more than `REFRESH_INTERVAL` (300 ms)
additional latency before flushing the control file, which is
negligible.

2024-11-12 15:17:03 +00:00

..

benches

Remove unused allow's (#6760)

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

scripts

Switch compute-related locales to C.UTF-8 by default

2024-11-08 12:19:18 -06:00

src

safekeeper: don't flush control file on WAL ingest path (#9698)

2024-11-12 15:17:03 +00:00

tests

Remove sync postgres_backend, tidy up its split usage.

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

Cargo.toml

Rename hyper 1.0 to hyper and hyper 0.14 to hyper0 (#9254)

2024-10-03 16:33:43 +02:00