Skip to content

Fix PGRST002 errors not logging the JSON messages and reloading the schema unnecessarily on startup#4367

Merged
laurenceisla merged 2 commits intoPostgREST:mainfrom
laurenceisla:fix/startup-503-errs
Oct 20, 2025
Merged

Fix PGRST002 errors not logging the JSON messages and reloading the schema unnecessarily on startup#4367
laurenceisla merged 2 commits intoPostgREST:mainfrom
laurenceisla:fix/startup-503-errs

Conversation

@laurenceisla
Copy link
Copy Markdown
Member

Closes #4129 as mentioned in the revision #4129 (comment).

@laurenceisla laurenceisla changed the title Fix 503 errors not logging the JSON messages and reloading the schema unnecessarily on startup Fix PGRST002 errors not logging the JSON messages and reloading the schema unnecessarily on startup Oct 8, 2025
@laurenceisla laurenceisla marked this pull request as ready for review October 8, 2025 06:20
@laurenceisla laurenceisla force-pushed the fix/startup-503-errs branch 2 times, most recently from 39886b2 to a2bb823 Compare October 15, 2025 01:35
It happens right after the configuration is loaded and before
the schema cache is queried.
When 503 errors happen if the Schema Cache is empty,
it should not retrigger the connection worker since
there's no Schema Cache loaded yet.
@laurenceisla laurenceisla merged commit ea5db2a into PostgREST:main Oct 20, 2025
33 checks passed
@laurenceisla laurenceisla deleted the fix/startup-503-errs branch October 20, 2025 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Requests are rejected immediately when loading the Schema Cache on startup

2 participants