Allow viewing ongoing queries and aborting them#26887
Merged
joshenlim merged 7 commits intoJun 4, 2024
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Ignored Deployments
|
|
No changes detected in Branching Preview Branches by Supabase. |
ivasilov
reviewed
May 30, 2024
alaister
approved these changes
May 31, 2024
alaister
left a comment
Member
There was a problem hiding this comment.
LGTM! Couple of comments though:
ivasilov
approved these changes
Jun 3, 2024
encima
pushed a commit
that referenced
this pull request
Jun 4, 2024
* Allow viewing ongoing queries and aborting them * Fix * Add refresh button + shift view running queries CTA * Fix scrolling in SqlEditorMenu * Small styling fix for table editor menu schema selector error state
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The ongoing queries that are shown here are specifically those run by the postgres user in hopes to scope down to just queries that are run via the dashboard (to prevent aborting any system queries that might be important)