Hi, my app doesn't work properly. Can someone expl...
# orm-helpm
Martí Crespí
12/17/2021, 9:08 AMHi, my app doesn't work properly. Can someone explain how it should be configurated the connection_pool and limit for prisma client?
Martí Crespí
12/17/2021, 9:13 AMI have tried to modify both parameters to postgresql://user@pass@xxxxxxxx:5432/database?schema=database_*&connection_limit=40&pool_timeout=20*_
Martí Crespí
12/17/2021, 9:14 AMAnd before that, it was throwing an error timeout. And now it's throwing another error..
Martí Crespí
12/17/2021, 9:14 AMError in connector: Error querying the database: db error: FATAL: remaining connection slots are reserved for non-replication superuser connectionsMartí Crespí
12/17/2021, 9:15 AMHow I should configure the prisma client to work properly? Because in the other hand, there is the database configuration..
a
Adrian Duyzer
12/17/2021, 9:19 PMI think this depends on how you architect your app. In mine, I share the client. So I have a client.ts file:
Copy code
import { PrismaClient } from "@prisma/client";
const prisma = new PrismaClient();
export default prisma; Copy code
import prisma from "./prisma/client"; Copy code
const ratedOpportunities = await prisma.opportunity.findMany({...m
Martí Crespí
12/19/2021, 9:08 AMHi @Adrian Duyzer! Many thanks for your opinion. But are you connecting or disconnecting before-after each query? Or you are using lazy connection (without invoke these methods)?
Martí Crespí
12/19/2021, 9:15 AMIf I understand your code well, you share an unique prisma client instance on whole app, minimizing the database connection impact.
a
Adrian Duyzer
01/06/2022, 3:18 PMHey, sorry, I just saw this. Are you still having issues? To answer your question, yes, I share a client instance in the whole app. I’m not doing any connecting/disconnecting before or after queries. Incidentally this approach is from the Prisma docs.
3 Views