Fix PGRST002 errors not logging the JSON messages and reloading the schema unnecessarily on startup#4367
Merged
laurenceisla merged 2 commits intoPostgREST:mainfrom Oct 20, 2025
Conversation
319f1a5 to
794f22c
Compare
794f22c to
b1a49bd
Compare
b1a49bd to
c30a9d0
Compare
39886b2 to
a2bb823
Compare
a2bb823 to
6f2993a
Compare
6f2993a to
4ee98d7
Compare
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.
4ee98d7 to
95720c5
Compare
steve-chavez
approved these changes
Oct 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4129 as mentioned in the revision #4129 (comment).