---
next_cursor: eyJzY29yZSI6MCwic2VxIjoxOTgzLCJzaW5jZSI6bnVsbCwidG9vbCI6InBzY2FsZSIsInYiOjF9
has_more: false
next: https://sincecutoff.com/v1/changes.md?tool=pscale&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxOTgzLCJzaW5jZSI6bnVsbCwidG9vbCI6InBzY2FsZSIsInYiOjF9
items: 2
---
# sincecutoff.com changes: pscale

## pscale branch extensions enable and disable preloadable Postgres extensions (pscale, 2026-10-09)
Published 2026-10-19
- slug: pscale-branch-extensions-enable-and-disable-preloadable-postgres-extensions-775e95682c6c
- score: 0.97

How to use it:

When a Postgres branch’s extension catalog marks an extension `can_enable: true`, use `pscale branch extensions enable|disable` to toggle it; the command queues a branch change that may restart the database. Warn the user first, then track it with `resize status` or use `--wait`.

Examples:

```
pscale branch extensions enable <database> <branch> <extension> --org <org> --format json
```

```
pscale branch extensions disable <database> <branch> <extension> --org <org> --format json
```

```
pscale branch extensions enable <database> <branch> <extension> --org <org> --format json --wait --wait-timeout <duration>
```

- why_it_matters: Enable or disable a preloadable extension on a Postgres branch while preserving the branch's other selected libraries.
- before: The release note says users had to edit the preload parameter directly, which could drop other libraries from the list.
- sources: <https://github.com/planetscale/cli/releases/tag/v0.344.0>, <https://github.com/planetscale/cli/pull/1462>, <https://github.com/planetscale/cli/blob/v0.344.0/AGENTS.md>, <https://github.com/planetscale/cli/blob/v0.344.0/internal/cmd/branch/extensions.go>
- gotchas: "Version: v0.344.0"; "<database> (required): Database name."; "<branch> (required): Branch name."; "<extension> (required): Extension name; it must be listed for the branch and marked `can_enable: true`."; "--org <org> (required): Selects the organization for the resource command."; "--format json: Selects JSON output; the documented examples use it."; "--wait: Waits for the change request to complete before returning."; "--wait-timeout <duration>: Maximum time to wait when `--wait` is used; defaults to 10m."; "Prerequisite: The database must be PostgreSQL. Neki extensions are managed per configuration profile; Vitess databases are unsupported by this command."; "Prerequisite: The extension must appear in `pscale branch extensions list` and be marked `can_enable: true`."; "Prerequisite: Authenticate with `pscale auth login`; for headless/CI use `--service-token-id` and `--service-token` on the command."; "Postgres only; Neki uses `branch config-profile extensions enable|disable`."; "The extension must have `can_enable: true`."; "The change queues a branch change and may restart the database."; "Extensions loaded with `CREATE EXTENSION` are outside this flow."

## pscale deploy-request retry for failed operations (pscale, 2026-10-09)
Published 2026-10-19
- slug: pscale-deploy-request-retry-for-failed-operations-80c90409effb
- score: 0.92

How to use it:

When a Vitess deploy request has a partial migration failure, retry its failed tables with `pscale deploy-request retry <database> <number>`.

Examples:

```
pscale deploy-request retry <database> <number>
```

- why_it_matters: Retry a failed operation associated with a deploy request.
- sources: <https://github.com/planetscale/cli/releases/tag/v0.344.0>, <https://planetscale.com/changelog/retry-partially-failed-deploy-request>
- gotchas: "Version: v0.344.0"; "<database> (required): Database name."; "<number> (required): Deploy request number."; "Prerequisite: Applies to Vitess deploy requests."

Next: https://sincecutoff.com/v1/changes.md?tool=pscale&score=0&cursor=eyJzY29yZSI6MCwic2VxIjoxOTgzLCJzaW5jZSI6bnVsbCwidG9vbCI6InBzY2FsZSIsInYiOjF9
Save `next_cursor`; next visit, pass it to get only what was published since.
<!-- end of page -->