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
Server Version: 2.35.1
CLI Version (for CLI related issue): -
Environment
OSS
What is the current behaviour?
It's impossible to use the Hasura console. Every action taken hangs the PostgreSQL database, causing it to reach 100% CPU usage, and it becomes impossible to do anything. Currently, we have 220 tables and 13 schemas, and it's not possible to work.
What is the expected behaviour?
That it works correctly, that it is fast, and that actions are instantaneous or, at the very least, quick.
How to reproduce the issue?
Create a database with 10 or 20 schemas and around 200 or 300 tables with permissions and relationships among them. Then try to create a column, change a unique key, or perform any other action.
Screenshots or Screencast
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
Change metadata system...
Keywords
console, metadata, postgres
The text was updated successfully, but these errors were encountered:
I faced with the same issue initially, But later I found out that there are some trigger actions running when we run a migration in background. Make sure this is not the case with you.
Version Information
Server Version: 2.35.1
CLI Version (for CLI related issue): -
Environment
OSS
What is the current behaviour?
It's impossible to use the Hasura console. Every action taken hangs the PostgreSQL database, causing it to reach 100% CPU usage, and it becomes impossible to do anything. Currently, we have 220 tables and 13 schemas, and it's not possible to work.
What is the expected behaviour?
That it works correctly, that it is fast, and that actions are instantaneous or, at the very least, quick.
How to reproduce the issue?
Create a database with 10 or 20 schemas and around 200 or 300 tables with permissions and relationships among them. Then try to create a column, change a unique key, or perform any other action.
Screenshots or Screencast
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
Change metadata system...
Keywords
console, metadata, postgres
The text was updated successfully, but these errors were encountered: