Advanced features on Prisma Postgres?
I'm evaluating potentially using Prisma's managed, serverless postgres offering. However, I'm trying to figure out the limitations of it vs managing my own postgres.
Main things i'm curious about are whether Prisma Postgres can support:
1. triggers
2. notify/listen events
3. materialized views
4. generated columns
5. extensions (pgvector, pgcron, tsvector/query etc)
1 Reply
You've gone full bot mode! Let me fetch that AI answer for you ASAP.
Certainly! Here’s a summary of advanced feature support in Prisma Postgres, based on the latest available information:
1. Triggers
Prisma Postgres (and Prisma ORM) does not natively support managing or introspecting PostgreSQL triggers. You can create triggers manually via custom SQL migrations, but Prisma does not provide a way to define or interact with them in the Prisma schema or Client. Real-time event triggers (e.g., for LISTEN/NOTIFY) are not yet supported natively, though there are community workarounds and feature requests open for this functionality see discussion. 2. NOTIFY/LISTEN Events
Direct support for NOTIFY/LISTEN is not available in Prisma ORM or Prisma Postgres. You would need to implement this outside of Prisma, using a separate Postgres client or library. There are open feature requests, but no official support as of now see issue. 3. Materialized Views
Materialized views are not natively supported in Prisma ORM or Prisma Postgres. You can manually create them and access them via raw SQL or TypedSQL, but Prisma does not introspect or manage them directly. Workarounds exist, such as creating shadow tables for introspection, but these are not first-class features see issue. 4. Generated Columns
The knowledge sources do not provide explicit information about support for generated columns in Prisma Postgres. If you need this feature, you may need to manage it manually via custom migrations and raw SQL. 5. Extensions (pgvector, pgcron, tsvector/query, etc.)
Prisma Postgres supports several extensions, including
Prisma Postgres is adding support for advanced Postgres features, especially extensions, but triggers, NOTIFY/LISTEN, and materialized views are not natively managed. For these, manual SQL and workarounds are required. Extension support is strong and growing, but always check the current list for your needs. ✅ Great, thanks for letting us know that this solved your question!
Prisma Postgres (and Prisma ORM) does not natively support managing or introspecting PostgreSQL triggers. You can create triggers manually via custom SQL migrations, but Prisma does not provide a way to define or interact with them in the Prisma schema or Client. Real-time event triggers (e.g., for LISTEN/NOTIFY) are not yet supported natively, though there are community workarounds and feature requests open for this functionality see discussion. 2. NOTIFY/LISTEN Events
Direct support for NOTIFY/LISTEN is not available in Prisma ORM or Prisma Postgres. You would need to implement this outside of Prisma, using a separate Postgres client or library. There are open feature requests, but no official support as of now see issue. 3. Materialized Views
Materialized views are not natively supported in Prisma ORM or Prisma Postgres. You can manually create them and access them via raw SQL or TypedSQL, but Prisma does not introspect or manage them directly. Workarounds exist, such as creating shadow tables for introspection, but these are not first-class features see issue. 4. Generated Columns
The knowledge sources do not provide explicit information about support for generated columns in Prisma Postgres. If you need this feature, you may need to manage it manually via custom migrations and raw SQL. 5. Extensions (pgvector, pgcron, tsvector/query, etc.)
Prisma Postgres supports several extensions, including
pgvector, citext, pg_trgm, fuzzystrmatch, pg_search, and more. Support for extensions is in Early Access and available on new instances. Native ORM support for some types (like pgvector) is coming soon, but for now, you must use custom migratio
ns and raw SQL/TypedSQL for unsupported types see docs.
Summary:Prisma Postgres is adding support for advanced Postgres features, especially extensions, but triggers, NOTIFY/LISTEN, and materialized views are not natively managed. For these, manual SQL and workarounds are required. Extension support is strong and growing, but always check the current list for your needs. ✅ Great, thanks for letting us know that this solved your question!