From 78f231c87ab008c1c5b58eb5fb8eecf0f78f4503 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20K=C5=82eczek?= Date: Tue, 10 Feb 2026 10:39:21 +0100 Subject: [PATCH] refactor: failure in schema cache load should not set listener delay Listener has its own backoff logic independent of schema cache loading. It also uses listener delay value to identify its retries and to trigger schema cache reloads upon failures. If schema cache reloading sets listener delay it might lead to some unexpected reloading loops. That's especially important in set ups where listener connection points to master and the pool to replica(s). --- src/PostgREST/AppState.hs | 1 - 1 file changed, 1 deletion(-) diff --git a/src/PostgREST/AppState.hs b/src/PostgREST/AppState.hs index 7841d3080..d24451089 100644 --- a/src/PostgREST/AppState.hs +++ b/src/PostgREST/AppState.hs @@ -364,7 +364,6 @@ retryingSchemaCacheLoad appState@AppState{stateObserver=observer, stateMainThrea when (rsIterNumber > 0) $ do let delay = fromMaybe 0 rsPreviousDelay `div` oneSecondInUs observer $ ConnectionRetryObs delay - putNextListenerDelay appState delay flushPool appState