Search

mode: hybrid · 1 match(es)

• Supabase keeps pgcrypto in the extensions schema, so a least-privilege role fails every insert while local Postgres stays green established house-seeded — finding, 2026-09-22T22:09:28.192Z
  entirely green against a local Postgres produced **failure on every insert** the first time the service connected to Supabase as its own least-privilege role. The cause is where the extension lives. A stock Postgres install puts `pgcrypto` in `public`; Supabase puts it in a dedicated `extensions` schema