Prisma db pull Extremely Slow on Supabase with Custom Schema
Issue: Prisma
Details:
- Using PostgreSQL on Supabase
- Prisma version:
- Debug logs show it gets stuck at:
Has anyone faced this before? Any fixes?
db pulldb pull is extremely slow when introspecting a schema on Supabase.Details:
- Using PostgreSQL on Supabase
- Prisma version:
prisma : 5.17.0
@prisma/client : 5.17.0
Computed binaryTarget : windows
Operating System : win32
Architecture : x64
Node.js : v22.14.0
Query Engine (Node-API) : libquery-engine 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine : schema-engine-cli 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm : @prisma/prisma-schema-wasm 5.17.0-31.393aa359c9ad4a4bb28630fb5613f9c281cde053
Default Engines Hash : 393aa359c9ad4a4bb28630fb5613f9c281cde053
Studio : 0.502.0
Preview Features : multiSchemaprisma : 5.17.0
@prisma/client : 5.17.0
Computed binaryTarget : windows
Operating System : win32
Architecture : x64
Node.js : v22.14.0
Query Engine (Node-API) : libquery-engine 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine : schema-engine-cli 393aa359c9ad4a4bb28630fb5613f9c281cde053 (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm : @prisma/prisma-schema-wasm 5.17.0-31.393aa359c9ad4a4bb28630fb5613f9c281cde053
Default Engines Hash : 393aa359c9ad4a4bb28630fb5613f9c281cde053
Studio : 0.502.0
Preview Features : multiSchema- Debug logs show it gets stuck at:
PS D:\Gitlab\Project - Copy> prisma db pull
Prisma schema loaded from prisma\schema.prisma
Environment variables loaded from .env
Datasource "db": PostgreSQL database "postgres", schemas "project-schema" at "aws-0-us-east-1.pooler.supabase.com:6543"
⠼ Introspecting based on datasource defined in prisma\schema.prismaPS D:\Gitlab\Project - Copy> prisma db pull
Prisma schema loaded from prisma\schema.prisma
Environment variables loaded from .env
Datasource "db": PostgreSQL database "postgres", schemas "project-schema" at "aws-0-us-east-1.pooler.supabase.com:6543"
⠼ Introspecting based on datasource defined in prisma\schema.prismaHas anyone faced this before? Any fixes?
