Process List

See the sessions connected to your server, find slow or blocking queries, and cancel or kill them.

The Process List shows every session connected to the server and what it is running. Use it to find long-running queries, idle transactions holding locks, or sessions you need to stop.

Open the Process List

Choose View ▸ Process List (⌥⌘P). It opens in its own window, titled Processes — <connection>, and remembers its size and position per connection.

The Process List uses its own database session. That means it keeps working — and can kill the culprit — even when a query is blocking your main window.

Supported engines

EngineSourcePrivileges needed
PostgreSQL 10+ (including Neon and Supabase)pg_stat_activity, client backends only—
MySQL / MariaDBinformation_schema.PROCESSLISTPROCESS to see other users' sessions
SQL Serversys.dm_exec_sessionsVIEW SERVER STATE

The Process List isn't available for SQLite, CockroachDB or Redshift.

Controls

ControlDescription
Filter sessionsNarrow the list by typing.
Hide idleHide idle and sleep sessions. Sessions that are idle in a transaction are never hidden.
Auto refreshOn by default; refreshes every 2 seconds.
RefreshReload now (⌘R).
Cancel QueryStop the running statement; the session stays connected.
Kill SessionDisconnect the session and roll back its open transaction.

The footer shows "N of M sessions" and the connection's safe mode.

Columns

ColumnDescription
PIDThe session or process id.
UserThe database user.
DatabaseThe database in use.
ClientThe client host.
ApplicationThe application name, when the client sets one.
StateThe session state. Active sessions are green; idle in transaction is amber.
TimeElapsed time.
QueryThe current or last statement.

Actions

Select a session and use the buttons, or right-click it:

  • Cancel Query — stop the statement but keep the session.
  • Kill Session — end the session.
  • Copy Query — copy its SQL.

On SQL Server, Cancel Query is disabled and Kill Session runs KILL <id>.

Safety

  • Killing a session always asks for confirmation, even when safe mode is Silent.
  • Killing is blocked on Read only connections.
  • You can't kill the Process List's own session.
  • Kills are recorded in the connection's history.