[!NOTE] This change has now been fully rolled out - thank you everyone for the feedback! ๐
We're excited to introduce Database Connections as a feature preview ๐
When your app is slow or hanging, the cause is usually happening at the database level โ a query that's stuck, one session blocking a dozen others, or a connection pool running dry. Postgres actually surfaces all of this through pg_stat_activity, but figuring out which query, which session, or what's holding the lock usually means knowing which system view to query and how to read it โ not something you want to learn mid-incident.
Database Connections gives you a live view of what's happening on your database right now, without writing SQL:
- See every active session, its query, and how long it's been running
- Get flagged the moment something's idle in transaction, blocked, or running longer than expected
- Trace a blocked query back to the session actually holding the lock โ even through multiple hops
- Terminate the stuck session directly from the table
- Ask the AI Assistant to summarize current activity in plain English
What we'd like to know from you#
- Any bugs or issues that you might have run into while using the Database Connections page
- Any ideas or suggestions that you reckon will improve the DX based on how you debug or diagnose stucked queries on your database
- Feel free to leave any feedback in this thread too! (Both good and bad!) ๐๐