---
title: blossom database:maintenance:enable
url: "/docs/reference/cli/database/maintenance/enable/"
canonical_url: https://docs.blossom88.com/docs/reference/cli/database/maintenance/enable/
markdown_url: https://docs.blossom88.com/docs/reference/cli/database/maintenance/enable.md
summary: Block connections to one PostgreSQL database
categories:
- cli
- reference
---

# blossom database:maintenance:enable

Block connections to one PostgreSQL database

## Usage

    blossom database:maintenance:enable --id ID [--follow] [--timestamps] [--yes]

## Flags

| Flag | Description |
| --- | --- |
| `--id (required)` | Database id |
| `--follow, -f` | Follow maintenance Activity until completion |
| `--timestamps` | Show log timestamps. Default: true. |
| `--yes, -y` | Confirm disconnecting clients of this database |

Block ordinary connections to one PostgreSQL database, then disconnect its
existing clients. Other databases in the instance keep working.

    blossom database:maintenance:show --id database-123
    blossom database:maintenance:enable --id database-123 --follow

The command shows connected Environments and asks for confirmation. External
clients may also use the database. Pass `--yes` for an already approved script.
Stop application writers first; this command does not scale Services or enable
an Environment maintenance page.

The restriction stays in place across PostgreSQL restarts and database
recreation until you explicitly disable it. Local administrative access remains
available for backups and recovery; customer connections cannot use that path.
Blossom logical backups continue to work during maintenance.

Currently supported on standalone PostgreSQL instances, Shared or Dedicated,
without replicas or a standby. A failed operation may leave access restricted:
inspect its Activity, then retry enable or explicitly disable. Never assume
clients are disconnected until the Activity succeeds.