Michał KłeczekandSteve Chavez 54430c3a2c fix: Do not clear the schema cache during retries ...

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.

2026-06-11 13:14:37 -05:00

..

doc

refactor: move dumpQi to Config.hs and clarify quoteQi

2025-10-30 12:26:29 -05:00

io

fix: Do not clear the schema cache during retries

2026-06-11 13:14:37 -05:00

load

nix(loadtest): move errors into mixed

2026-06-01 20:49:35 +00:00

memory

fix: shutdown should wait for in flight requests

2026-04-20 16:19:13 -05:00

observability

refactor(config): use correct data type for server-cors-allowed-origins

2026-06-09 12:35:47 +00:00

pgbench

nix: shorten postgrest-with-postgresql-xx scripts

2025-11-18 09:40:16 +00:00

spec

test: move cors related tests from io tests to spec tests

2026-06-10 10:27:49 +00:00

coverage.overlay

cov: empty coverage overlay (#2119)

2022-01-07 13:06:03 -05:00

weeder.toml

nix: Update nixpkgs and build with GHC 9.4.8

2024-01-18 18:54:33 +01:00