Turn a Supabase RPC ambiguity error into a support-ready packet.

Paste redacted PostgREST RPC notes and separate stale function signatures, unsupported overloads, argument-name mismatches, schema reload evidence, and raw PostgreSQL 42725 ambiguity before changing RLS or bypassing RPC.

Build packet See fixed-scope report

Prove the function signatureCapture pg_proc, argument names, argument types, result type, exposed schema, and callable role evidence.

Separate cache from overloadsPGRST202, PGRST203, and PostgreSQL 42725 point to different next checks.

Avoid risky shortcutsDo not replace RPC with broad table access or a privileged function until the packet shows the real failure mode.

Project label

Context

Redacted RPC error, SQL, and migration notes Evidence already captured

RPC error includes the code and route, such as /rpc/name, PGRST202, PGRST203, or 42725 pg_proc query records proname, oid, arguments, result type, namespace, and row count Direct SQL invocation result is recorded separately from REST/RPC behavior Supabase .rpc() body or REST request argument names are recorded and redacted Any overloads, same argument names with different types, unnamed JSON/jsonb parameters, or dropped signatures are listed Return type evidence is captured, including RETURNS SETOF, quoted table names, or json/jsonb NOTIFY pgrst, 'reload schema', restart, version, or queue-refresh evidence is recorded Function grants, RLS, SECURITY DEFINER, and search_path are reviewed separately from ambiguity

This page runs locally in the browser. Paste only redacted notes. Do not paste database URLs, passwords, JWT secrets, service-role keys, project secrets, real user rows, private screenshots, payment data, full names, private handles, or private account records.

Ready.

Want a 24h second pass on this RPC packet?

If the checker finds several launch-critical gaps, the fixed-scope Supabase report can review one redacted packet: function signature evidence, RPC request shape, overload ambiguity, schema reload evidence, grants/RLS separation, and next smoke tests.

Check paid report scope Read sample report

RPC ambiguity review packet

What this checks

Whether PostgREST cannot find a function signature, cannot choose among overloads, or is forwarding a raw PostgreSQL ambiguity error.
Whether argument names in the request match function parameters after identifier casing and quoting rules are considered.
Whether direct SQL succeeds while REST/RPC fails, which is important evidence for schema-cache or PostgREST resolution issues.
Whether a workaround changes authorization risk by bypassing RPC, widening table grants, or adding a privileged function.

PostgREST functionsRPC behavior, argument mapping, return types, and overload limits. PostgREST errorsPGRST202 and PGRST203 schema-cache and overload guidance. Supabase reloadManaged PostgREST schema reload with NOTIFY pgrst. Exact issueCurrent Supabase RPC 42725 function ambiguity report.