Skip to content

Fix connection string parameter for pooling #7567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nurul3101 merged 1 commit into from
Feb 26, 2026
Merged

Fix connection string parameter for pooling #7567

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions apps/docs/content/docs/postgres/database/connection-pooling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,14 +16,14 @@ Prisma Postgres supports connection pooling through [TCP connections](#connectio
TCP connection pooling is currently in [Early Access](/console/more/feature-maturity#early-access).
:::

To use a pooled connection, append `&pooled=true` to your Prisma Postgres TCP connection string:
To use a pooled connection, append `&pool=true` to your Prisma Postgres TCP connection string:

```bash
# Direct connection (no pooling)
DATABASE_URL="postgres://USER:PASSWORD@db.prisma.io:5432/?sslmode=require"

# Pooled connection
DATABASE_URL="postgres://USER:PASSWORD@db.prisma.io:5432/?sslmode=require&pooled=true"
DATABASE_URL="postgres://USER:PASSWORD@db.prisma.io:5432/?sslmode=require&pool=true"
```

You can also enable connection pooling when generating your connection string in the [Prisma Console](https://console.prisma.io) by toggling on the **pooling** option.
Expand Down
Loading