# Troubleshooting (/docs/postgres/troubleshooting)

> For the complete Prisma documentation index, see [llms.txt](https://www.prisma.io/docs/llms.txt). A markdown version of any docs page is available by appending `.md` to its URL.

Resolve common issues with Prisma Postgres

Location: Postgres > Troubleshooting

This guide helps resolve common issues when working with Prisma Postgres.

## The `--db` option is not recognized when running `prisma init` [#the---db-option-is-not-recognized-when-running-prisma-init]

### Problem [#problem]

Running the following command fails because the `--db` option is not recognized:

  

#### bun

```bash
bunx --bun prisma init --db
```

#### pnpm

```bash
pnpm prisma init --db
```

#### yarn

```bash
yarn prisma init --db
```

#### npm

```bash
npx prisma init --db
```

### Cause [#cause]

This can occur due to npx caching. If you've previously run `npx prisma init`, your machine may be using an outdated cached version that doesn't recognize the `--db` flag because it was only introduced in a later version of Prisma ORM.

### Solution [#solution]

Explicitly run the Prisma ORM 7 CLI through its `prev` dist-tag:

  

#### bun

```bash
bunx --bun prisma@prev init --db
```

#### pnpm

```bash
pnpm dlx prisma@prev init --db
```

#### yarn

```bash
yarn dlx prisma@prev init --db
```

#### npm

```bash
npx prisma@prev init --db
```

This runs the latest Prisma ORM 7 CLI, which supports the flag, preventing issues with outdated command syntax.

## Workspace plan limit reached when running `prisma init --db` [#workspace-plan-limit-reached-when-running-prisma-init---db]

### Problem [#problem-1]

When running the command:

  

#### bun

```bash
bunx --bun prisma@prev init --db
```

#### pnpm

```bash
pnpm dlx prisma@prev init --db
```

#### yarn

```bash
yarn dlx prisma@prev init --db
```

#### npm

```bash
npx prisma@prev init --db
```

You may encounter the following error message in your logs:

```
Workspace plan limit reached for feature "Project".
```

### Cause [#cause-1]

Your default [workspace](https://www.prisma.io/docs/console/concepts#workspace) project limit has been reached.

### Solution [#solution-1]

To resolve this issue, consider the following options:

* Configure a different Workspace as your default, one that has available capacity for additional projects.
* Delete unused projects or databases from your current default Workspace to free up space.
* Ensure that you are logged into the correct account in the Prisma CLI. For more details on authentication and account management, please refer to the [Prisma CLI documentation](https://www.prisma.io/docs/cli/v7/console).
* [Upgrade to a plan](https://www.prisma.io/docs/postgres#billing-and-limits) that supports more projects in your default Workspace.

## Related pages

- [`Best Postgres for AI apps`](https://www.prisma.io/docs/postgres/best-postgres-for-ai-apps): Why Prisma Postgres works well for AI and LLM workloads: built-in pooling, edge connectivity, pgvector, and MCP support.
- [`create-db`](https://www.prisma.io/docs/postgres/npx-create-db): Learn how to provision temporary Prisma Postgres databases with create-db
- [`Database`](https://www.prisma.io/docs/postgres/database): Overview of Prisma Postgres database operations, connections, pooling, backups, and query analysis.
- [`Error reference`](https://www.prisma.io/docs/postgres/error-reference): Error reference documentation for Prisma Postgres
- [`Import from existing database`](https://www.prisma.io/docs/postgres/import-from-existing-database): Choose the right path to import data from PostgreSQL or MySQL into Prisma Postgres.