Supabase db diff command gives RangeError: Maximum call stack size exceeded error

[Dudeonyx]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Running supabase db diff -f <path> --local
2. See error

Applying migration 20251213231033_profiles_admin_dashboard.sql...
Diffing schemas...

error diffing schema: error running container: exit 1:                                                    

RangeError: Maximum call stack size exceeded                                                              

    at Object.get (ext:deno_node/_process/process.ts:41:8)                                                

    at quoted_identifier (file:///var/tmp/sb-compile-edge-runtime/node_modules/localhost/@pgkit/schemainspect/0.6.1/dist/misc.js:70:41)
    at InspectedSelectable.get quoted_full_name (file:///var/tmp/sb-compile-edge-runtime/node_modules/localhost/@pgkit/schemainspect/0.6.1/dist/inspected.js:19:45)
    at InspectedSelectable.get signature (file:///var/tmp/sb-compile-edge-runtime/node_modules/localhost/@pgkit/schemainspect/0.6.1/dist/inspected.js:22:21)
    at get_related_for_item (file:///var/tmp/sb-compile-edge-runtime/node_modules/localhost/@pgkit/schemainspect/0.6.1/dist/pg/obj.js:1077:26)
    at file:///var/tmp/sb-compile-edge-runtime/node_modules/localhost/@pgkit/schemainspect/0.6.1/dist/pg/obj.js:1077:76
    at Array.flatMap (<anonymous>)                                                                        

    at get_related_for_item (file:///var/tmp/sb-compile-edge-runtime/node_modules/localhost/@pgkit/schemainspect/0.6.1/dist/pg/obj.js:1077:63)
    at file:///var/tmp/sb-compile-edge-runtime/node_modules/localhost/@pgkit/schemainspect/0.6.1/dist/pg/obj.js:1077:76
    at Array.flatMap (<anonymous>)                                                                        

main worker has been destroyed

Expected behavior Not error out and produce a schema diff, this is a small project with about 20 tables, half unused so far, but supabase db reset works as expected Using --use-pg-schema flag works fine as well, leading me to believe the issue is with migra

Screenshots

System information

• Ticket ID: bad3728094b148d390bfc872c2a869a0
• Version of OS: Windows 11
• Version of CLI: v2.67.1
• Version of Docker: v28.5.1, build e180ab8
• Versions of services: SERVICE IMAGE | LOCAL | LINKED ------------------------|------------------------|------------ supabase/postgres | 17.6.1.009 | 17.6.1.009 supabase/gotrue | v2.184.0 | v2.184.0 postgrest/postgrest | v13.0.5 | v13.0.5 supabase/realtime | v2.68.4 | - supabase/storage-api | v1.33.0 | v1.31.1 supabase/edge-runtime | v1.69.28 | - supabase/studio | 2025.12.09-sha-434634f | - supabase/postgres-meta | v0.95.1 | - supabase/logflare | 1.27.0 | - supabase/supavisor | 2.7.4 | -

Additional context If applicable, add any other context about the problem here.

• Version of supabase-js v2.87.1
• Version of Node.js v24.6.0
• I don't know if its relevant but I recently updated deno from v2.5.6 to v2.6