From 2656f695d4d81dbc3b6cd962cdd8d253a567db42 Mon Sep 17 00:00:00 2001 From: Gregory Boch Personal Date: Mon, 12 Oct 2026 10:46:45 +0200 Subject: [PATCH 1/2] docs(skills): Prisma Postgres has no query cache; backups are paid-plan only The Prisma Postgres section of prisma-platform-core-concepts listed "optional query caching" and unqualified automated backups. The Postgres FAQ says Prisma Postgres has no query cache of its own, and the backups page says snapshots exist on Starter, Pro and Business only. Closes #344 Co-Authored-By: Claude Opus 5.5 --- skills/prisma-platform-core-concepts/SKILL.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/skills/prisma-platform-core-concepts/SKILL.md b/skills/prisma-platform-core-concepts/SKILL.md index 5b7045a7..46d44972 100644 --- a/skills/prisma-platform-core-concepts/SKILL.md +++ b/skills/prisma-platform-core-concepts/SKILL.md @@ -268,15 +268,16 @@ inside a service; sleeping makes them silently unreliable. To your application, a Prisma Postgres database is a regular PostgreSQL database behind a connection string: any client works, including Prisma ORM, psql, Kysely, and Drizzle. On top of plain PostgreSQL each database has -built-in connection pooling (no PgBouncer to run), optional query caching, -and automated backups. +built-in connection pooling (no PgBouncer to run) and, on paid plans, +automated daily backups. Databases usually come from deploying a module that declares one. They can also be created directly, in which case the connection URL prints exactly once. Additional connection strings can be minted and rotated per database; every secret is shown exactly once at creation, and no later read reveals -it. Backups are automated, listable, and restorable, and per-database usage -metrics are queryable; the `postgres` group covers all of it. +it. On paid plans, backups are automated, listable, and restorable. +Per-database usage metrics are queryable; the `postgres` group covers all of +it. ## Object storage From 142b671e4fe39f3a5eff9e1f348ebbf96393f667 Mon Sep 17 00:00:00 2001 From: Gregory Boch Personal Date: Mon, 12 Oct 2026 10:51:35 +0200 Subject: [PATCH 2/2] docs(skills): snapshots are taken on days with database activity Co-Authored-By: Claude Opus 5.5 --- skills/prisma-platform-core-concepts/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/prisma-platform-core-concepts/SKILL.md b/skills/prisma-platform-core-concepts/SKILL.md index 46d44972..a2c372e0 100644 --- a/skills/prisma-platform-core-concepts/SKILL.md +++ b/skills/prisma-platform-core-concepts/SKILL.md @@ -269,7 +269,7 @@ To your application, a Prisma Postgres database is a regular PostgreSQL database behind a connection string: any client works, including Prisma ORM, psql, Kysely, and Drizzle. On top of plain PostgreSQL each database has built-in connection pooling (no PgBouncer to run) and, on paid plans, -automated daily backups. +automated backups: a snapshot each day the database has activity. Databases usually come from deploying a module that declares one. They can also be created directly, in which case the connection URL prints exactly