jimmy/postgrest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: Do not clear the schema cache during retries

Browse Source 
retryingSchemaCacheLoad should not clear existing schema cache upon failure - there is no reason to do that. If there is a communication issue with the database server or db is down, clients are going to get 502 anyway. If it was a glitch when loading the schema cache - the clients are going to use old (stale) schema cache for some time until next retry re-loads it successfully.
This commit is contained in:
Michał Kłeczek
2026-06-11 13:14:37 -05:00
committed by Steve Chavez
parent e9a016670f
commit 54430c3a2c
3 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/io/test_io.py
+1 -1
View File
@@ -763,7 +763,7 @@ def test_admin_ready_includes_schema_cache_state(defaultenv, metapostgrest):
assert response.status_code == 503
response = postgrest.session.get("/projects", timeout=1)
assert response.status_code == 503
assert response.status_code == 200
reset_statement_timeout(metapostgrest, role)