SS-1930 Add automatic cleanup for idle Postgres sessions#542
Merged
Conversation
j-awada
approved these changes
Jun 8, 2026
j-awada
left a comment
Contributor
There was a problem hiding this comment.
Works as expected locally and LGTM.
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.
Description
This PR relates to SS-1930.
Adds PostgreSQL session timeout configuration for Studio database connections so idle sessions are cleaned up automatically. The defaults are:
POSTGRES_IDLE_SESSION_TIMEOUT=30mPOSTGRES_IDLE_IN_TRANSACTION_SESSION_TIMEOUT=10mThe Django database configuration now passes these values through PostgreSQL connection options and enables
CONN_HEALTH_CHECKS, so pooled connections are checked before reuse if PostgreSQL has closed an idle connection. The new environment variables are also documented in.env.template.Checklist