Fix Postgres "idle in transaction" when getting current user #15
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.
When interacting with a Postgres database, particularly during the process of querying user info, I found that the database connection remains persistently open in an
idle in transaction
state. This issue may lead to inefficient resource utilization and potential database locks. So I propose to add explicit rollback command after the query operation. This will change connection state to a standardidle
Steps to reproduce