We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Each time NOTIFY pgrst is done, we log:
NOTIFY pgrst
09/Jan/2024:18:45:56 -0500: Starting PostgREST 11.2.0 (96ca177)... 09/Jan/2024:18:45:56 -0500: Attempting to connect to the database... 09/Jan/2024:18:45:56 -0500: Connection successful 09/Jan/2024:18:45:56 -0500: Config reloaded 09/Jan/2024:18:45:56 -0500: Schema cache loaded
The Starting PostgREST.. is misleading, as we're already started. It leads to believe the systemd service has restarted multiple times.
Starting PostgREST
Only log "Starting PostgREST" at startup not during reload.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Problem
Each time
NOTIFY pgrst
is done, we log:The
Starting PostgREST
.. is misleading, as we're already started. It leads to believe the systemd service has restarted multiple times.Solution
Only log "Starting PostgREST" at startup not during reload.
The text was updated successfully, but these errors were encountered: