pg_kill

Terminate specific database processes on Heroku to stop stuck queries, clear blocking transactions, manage resource-heavy operations, and handle runaway processes with controlled, optional force termination.

Instructions

Terminate specific database processes. Use this tool when you need to: 1) Stop problematic or stuck queries, 2) Clear blocking transactions, 3) Manage resource-intensive operations, 4) Handle runaway processes safely. The tool provides controlled process termination with optional force mode.

Input Schema

Name	Required	Description
`app`	Yes	The name of the Heroku app whose database process to terminate.
`database`	No	Config var containing the connection string, unique name, ID, or alias of the database. To access another app's database, prepend the app name to the config var or alias with `APP_NAME::`. If omitted, DATABASE_URL is used.
`force`	No	When true, forces immediate termination instead of graceful shutdown.
`pid`	Yes	The process ID to terminate, as shown by pg_ps.

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "app": {
      "description": "The name of the Heroku app whose database process to terminate.",
      "type": "string"
    },
    "database": {
      "description": "Config var containing the connection string, unique name, ID, or alias of the database. To access another app's database, prepend the app name to the config var or alias with `APP_NAME::`. If omitted, DATABASE_URL is used.",
      "type": "string"
    },
    "force": {
      "description": "When true, forces immediate termination instead of graceful shutdown.",
      "type": "boolean"
    },
    "pid": {
      "description": "The process ID to terminate, as shown by pg_ps.",
      "type": "number"
    }
  },
  "required": [
    "app",
    "pid"
  ],
  "type": "object"
}

Heroku MCP server

pg_kill

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Heroku MCP server

Related Tools