How do I install the Pscale Pgbouncer skill?

Run npx skillmds add vince-winkintel/pscale-pgbouncer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pscale Pgbouncer safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pscale Pgbouncer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pscale Pgbouncer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pscale Pgbouncer?

vince-winkintel (@vince-winkintel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pscale Pgbouncer by vince-winkintel

Name: Pscale Pgbouncer
Rating: 4.2 (5 reviews)
Author: vince-winkintel

Pscale Pgbouncer

Manage dedicated PostgreSQL PgBouncers with PlanetScale CLI. Use when listing or inspecting dedicated poolers, creating primary or replica poolers, changing PgBouncer size, replicas, traffic target, or parameters, monitoring/canceling asynchronous resize requests, or deleting a dedicated PgBouncer. Triggers on pscale pgbouncer, dedicated PgBouncer, Postgres pooler, bouncer resize, replica pooler, PGB SKU.

vince-winkintel b34d7c6 2 files · 16.0 KB Updated Sep 10, 2026

File contents

pscale pgbouncer

Manage dedicated PgBouncers for PlanetScale PostgreSQL branches. These are separate pooler services, not the local PgBouncer on port 6432 and not the pgbouncer.* parameters managed by pscale branch resize.

Inspect before changing

pscale pgbouncer list <database> <branch> --org <org> --format json
pscale pgbouncer show <database> <branch> <name> --org <org> --format json

This command group rejects Vitess databases. Use JSON output to preserve the exact name, target, SKU, replica count, parameters, and lifecycle metadata.

Create a dedicated PgBouncer

--target is required and accepts primary, replica, or replica_az_affinity. --name is optional and auto-generated when omitted; explicit names are at most 12 characters, and primary and replica are reserved. If --size is omitted, the API selects a default SKU.

The command help documents the explicit-name limit and reserved names.

pscale pgbouncer create <database> <branch> \
  --org <org> \
  --name read-pool \
  --target replica \
  --size PGB_10 \
  --replicas-per-cell 2 \
  --format json

Creation changes capacity and cost. Inspect the branch and existing poolers, propose the exact target/size/replica values, and obtain approval before creating one. Verify afterward with show.

Resize or reconfigure

resize can combine size, replicas per cell, traffic target, and repeatable namespace.name=value parameters in one asynchronous request.

pscale pgbouncer resize <database> <branch> <name> \
  --org <org> \
  --size PGB_10 \
  --replicas-per-cell 2 \
  --target replica \
  --parameters pgbouncer.default_pool_size=100 \
  --wait --wait-timeout 20m \
  --format json

Inspect show first and surface capacity, cost, routing, restart, and connection impact. Pass only intended changes. Without --wait, poll the latest request:

pscale pgbouncer resize status <database> <branch> <name> \
  --org <org> --format json

pending and resizing are non-terminal; completed and canceled are terminal. A request that already matches the current configuration returns a no_change result rather than a resize ID. After completion, verify both resize status and show.

Cancel an unfinished resize

pscale pgbouncer resize cancel <database> <branch> <name> \
  --org <org> --format json

Cancellation is an operational write. Confirm the latest request is unfinished, obtain approval, cancel exactly the intended pooler, then re-run status and show.

Delete a dedicated PgBouncer

Deletion removes a connection endpoint and can break clients. Show the pooler, confirm no clients depend on it, present the exact database/branch/name, and get explicit approval. Prefer the interactive confirmation; reserve --force for already-approved non-interactive automation.

pscale pgbouncer show <database> <branch> <name> --org <org> --format json
pscale pgbouncer delete <database> <branch> <name> --org <org>

# Non-interactive only after explicit approval
pscale pgbouncer delete <database> <branch> <name> --org <org> --force

Verify deletion by listing the branch's remaining PgBouncers.

See references/commands.md for captured command help.

---name: pscale-pgbouncerdescription: Manage dedicated PostgreSQL PgBouncers with PlanetScale CLI. Use when listing or inspecting dedicated poolers, creating primary or replica poolers, changing PgBouncer size, replicas, traffic target, or parameters, monitoring/canceling asynchronous resize requests, or deleting a dedicated PgBouncer. Triggers on pscale pgbouncer, dedicated PgBouncer, Postgres pooler, bouncer resize, replica pooler, PGB SKU.---# pscale pgbouncerManage dedicated PgBouncers for PlanetScale PostgreSQL branches. These are separate pooler services, not the local PgBouncer on port 6432 and not the `pgbouncer.*` parameters managed by `pscale branch resize`.## Inspect before changing```bashpscale pgbouncer list <database> <branch> --org <org> --format jsonpscale pgbouncer show <database> <branch> <name> --org <org> --format json```This command group rejects Vitess databases. Use JSON output to preserve the exact name, target, SKU, replica count, parameters, and lifecycle metadata.## Create a dedicated PgBouncer`--target` is required and accepts `primary`, `replica`, or `replica_az_affinity`. `--name` is optional and auto-generated when omitted; explicit names are at most 12 characters, and `primary` and `replica` are reserved. If `--size` is omitted, the API selects a default SKU.The command help documents the explicit-name limit and reserved names.```bashpscale pgbouncer create <database> <branch> \ --org <org> \ --name read-pool \ --target replica \ --size PGB_10 \ --replicas-per-cell 2 \ --format json```Creation changes capacity and cost. Inspect the branch and existing poolers, propose the exact target/size/replica values, and obtain approval before creating one. Verify afterward with `show`.## Resize or reconfigure`resize` can combine size, replicas per cell, traffic target, and repeatable `namespace.name=value` parameters in one asynchronous request.```bashpscale pgbouncer resize <database> <branch> <name> \ --org <org> \ --size PGB_10 \ --replicas-per-cell 2 \ --target replica \ --parameters pgbouncer.default_pool_size=100 \ --wait --wait-timeout 20m \ --format json```Inspect `show` first and surface capacity, cost, routing, restart, and connection impact. Pass only intended changes. Without `--wait`, poll the latest request:```bashpscale pgbouncer resize status <database> <branch> <name> \ --org <org> --format json````pending` and `resizing` are non-terminal; `completed` and `canceled` are terminal. A request that already matches the current configuration returns a `no_change` result rather than a resize ID. After completion, verify both `resize status` and `show`.## Cancel an unfinished resize```bashpscale pgbouncer resize cancel <database> <branch> <name> \ --org <org> --format json```Cancellation is an operational write. Confirm the latest request is unfinished, obtain approval, cancel exactly the intended pooler, then re-run `status` and `show`.## Delete a dedicated PgBouncerDeletion removes a connection endpoint and can break clients. Show the pooler, confirm no clients depend on it, present the exact database/branch/name, and get explicit approval. Prefer the interactive confirmation; reserve `--force` for already-approved non-interactive automation.```bashpscale pgbouncer show <database> <branch> <name> --org <org> --format jsonpscale pgbouncer delete <database> <branch> <name> --org <org># Non-interactive only after explicit approvalpscale pgbouncer delete <database> <branch> <name> --org <org> --force```Verify deletion by listing the branch's remaining PgBouncers.See [references/commands.md](references/commands.md) for captured command help.

Frequently asked questions