# What changed in @prisma/adapter-pg

> 6 changes in @prisma/adapter-pg 6 to 7 from its official release notes, upgrade guides and advisories: 5 breaking. Each one cited. Sources checked 2026-10-27. HTML: https://unstale.sh/npm/@prisma/adapter-pg/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @prisma/adapter-pg 7

### Breaking changes

- The adapter uses the underlying Node.js driver’s pool settings, which can differ from Prisma ORM v6 defaults; for example, pg has no connection timeout by default. (7.0.0) — [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/v7)
- Creating a Prisma Client now requires a driver adapter; PostgreSQL users pass a PrismaPg instance to PrismaClient. (7.0.0) — [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/v7)
- Invalid SSL certificates are no longer ignored by default; configure certificates or set ssl.rejectUnauthorized to false to keep the previous behavior. (7.0.0) — [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/v7)

### Behavior and default changes

- PrismaPg requires a direct database connection string and fails when passed a Prisma Accelerate URL. (7.0.0) — [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/v7)

## @prisma/adapter-pg 6

### Breaking changes

- Prisma ORM v6 requires Node.js 18.18.0, 20.9.0, or 22.11.0 at minimum; Node.js 16, 17, 19, and 21 are not officially supported. (6.0.0) — [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/v6)
- Prisma ORM v6 raises the minimum supported TypeScript version to 5.1.0. (6.0.0) — [upgrade guide](https://www.prisma.io/docs/guides/upgrade-prisma-orm/v6)