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
Not sure if we want to make this public, but just discovered you can use the SQL API to see your own long running queries and terminate them.
As you presales guys are keen on running long queries 😛, it could be useful to have this.
It will only work to see the queries ran with the API key, though, not for the public_user used for read-only calls.
select * from pg_stat_activity where usename=current_user
and select * pg_terminate_backend(pid)
You can only kill your own queries. Useful query to kill everything you have running: select pg_terminate_backend(pid) from pg_stat_activity where usename=current_user
The text was updated successfully, but these errors were encountered:
Not sure if we want to make this public, but just discovered you can use the SQL API to see your own long running queries and terminate them.
As you presales guys are keen on running long queries 😛, it could be useful to have this.
It will only work to see the queries ran with the API key, though, not for the public_user used for read-only calls.
select * from pg_stat_activity where usename=current_user
and
select * pg_terminate_backend(pid)
You can only kill your own queries. Useful query to kill everything you have running:
select pg_terminate_backend(pid) from pg_stat_activity where usename=current_user
The text was updated successfully, but these errors were encountered: