Chris
PPrisma
•Created by Manupa Samarawickrama on 1/25/2025 in #help-and-questions
Error During Migration: must be a member of pg_signal_backend in Supabase with Prisma on Serverless
AHHH fixed it by granting my postgres user with that privilege
-- Grant Prisma the ability to terminate backend processes (fixes migrate dev issue)
GRANT pg_signal_backend TO "prisma";
-- Ensure Prisma has full access to existing objects
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO "prisma";
GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public TO "prisma";
GRANT ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA public TO "prisma";
GRANT ALL PRIVILEGES ON ALL ROUTINES IN SCHEMA public TO "prisma";
-- Ensure Prisma has default privileges for any future objects
ALTER DEFAULT PRIVILEGES FOR ROLE postgres IN SCHEMA public GRANT ALL ON TABLES TO "prisma";
ALTER DEFAULT PRIVILEGES FOR ROLE postgres IN SCHEMA public GRANT ALL ON SEQUENCES TO "prisma";
ALTER DEFAULT PRIVILEGES FOR ROLE postgres IN SCHEMA public GRANT ALL ON ROUTINES TO "prisma";
Must be some docs I overlooked or something. Anyway, it works.
18 replies
PPrisma
•Created by Manupa Samarawickrama on 1/25/2025 in #help-and-questions
Error During Migration: must be a member of pg_signal_backend in Supabase with Prisma on Serverless
yarn prisma migrate deploy works fine, but yarn prisma migrate dev terminates before the migration files are even created locally so there is no deployment to do. It looks like there are some changes to supavisor on Supabase but not sure if related
18 replies
PPrisma
•Created by Manupa Samarawickrama on 1/25/2025 in #help-and-questions
Error During Migration: must be a member of pg_signal_backend in Supabase with Prisma on Serverless
Hi @Manupa Samarawickrama did you find a solution to this one. We've also encountered this issue. We have created a new user with the same issue as well as changed the connection strings in our prisma file
18 replies