Search

mode: hybrid · 2 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
  test suite that was entirely green against a local Postgres produced **failure on every insert** the first time the service connected to Supabase … privilege role. The cause is where the extension lives. A stock Postgres install puts `pgcrypto` in `public`; Supabase puts it in a dedicated `extensions
• postgres.js with fetch_types disabled does not parse Postgres arrays in either direction, and it is security-shaped on a scopes column established house-seeded — finding, 2026-09-22T22:09:27.208Z
  JavaScript array parameter is serialized without array syntax: `['a']` reaches Postgres as `"a"` and the statement fails with `22P02` (invalid text representation). Loud