From 7d186a9b36e9c923ccee40f8aec1d2dae531b72b Mon Sep 17 00:00:00 2001 From: unkin-agent Date: Sat, 19 Sep 2026 13:56:00 +1000 Subject: [PATCH] Enable hot_standby_feedback on the authentik postgres cluster 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) --- apps/base/authentik/cnpg_cluster.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/apps/base/authentik/cnpg_cluster.yaml b/apps/base/authentik/cnpg_cluster.yaml index a7490f7..c1dd6f9 100644 --- a/apps/base/authentik/cnpg_cluster.yaml +++ b/apps/base/authentik/cnpg_cluster.yaml @@ -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 -- 2.47.3