Enable hot_standby_feedback on the authentik postgres cluster
ci/woodpecker/pr/vector-test Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful

Slow authentik reads served by a hot standby exhaust
max_standby_streaming_delay and are cancelled with "conflict with
recovery", surfacing as HTTP 500s.

- set hot_standby_feedback on (SIGHUP reload, no restart)
This commit is contained in:
2026-09-19 13:56:00 +10:00
parent 34dd70435e
commit 7d186a9b36
+4
View File
@@ -66,6 +66,10 @@ spec:
dynamic_shared_memory_type: posix
effective_cache_size: 256MB
full_page_writes: "on"
# Replicas report their oldest xmin to the primary, so multi-second reads on
# a hot standby stop exhausting max_standby_streaming_delay and being
# cancelled. Retained-dead-tuple cost is negligible on a ~155MB database.
hot_standby_feedback: "on"
log_destination: csvlog
log_directory: /controller/log
log_filename: postgres