Skip to content
New issue

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

Queries are left running and consume all database CPU #38

Open
saulcosta opened this issue Jan 6, 2021 · 0 comments
Open

Queries are left running and consume all database CPU #38

saulcosta opened this issue Jan 6, 2021 · 0 comments

Comments

@saulcosta
Copy link

Hello!

When starting a console in read-only mode, a basic query (like a SELECT) is left running, even after the command has completed in the console itself. It appears to be the last query that was executed.

This results in the database's CPU usage continually climbing to a point where it finally is using almost all of the CPU. Once the query is killed or the console is closed, the CPU immediately drops to normal levels.

We are using gem version 0.5.0 and PostgreSQL 9.6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant