You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: