plpgsql_check causing "cannot find parent statement on pldbgapi2 call stack" error in recursive PL/pgSQL functions

I'm encountering an internal error in PL/pgSQL functions that stems from `plpgsql_check`, which Supabase appears to load automatically via shared_preload_libraries. It's highly unexpected that correct SQL code can fail due to a library injected at the platform level that the user has no control over. Users shouldn't need to debug Supabase's infrastructure choices to run standard PostgreSQL functions. The error occurs when running [pgstac](https://github.com/stac-utils/pgstac) during recursive PL/pgSQL function calls: ```sql psycopg.errors.InternalError_: cannot find parent statement on pldbgapi2 call stack CONTEXT: PL/pgSQL function run_or_queue(text) line 13 at RETURN SQL statement "SELECT run_or_queue(format($q$ UPDATE collections SET content = jsonb_set_lax( content, '{extent}'::text[], collection_extent(%L, FALSE), true, 'use_json_null' ) WHERE id=%L ; $q$, collection, collection))" PL/pgSQL function update_partition_stats(text,boolean) line 57 at PERFORM SQL statement "SELECT update_partition_stats('_items_1', 'f');" PL/pgSQL function run_or_queue(text) line 11 at EXECUTE SQL statement "SELECT run_or_queue( format('SELECT update_partition_stats(%L, %L);', _partition, istrigger) )" PL/pgSQL function update_partition_stats_q(text,boolean) line 4 at PERFORM ``` ## Investigation: I have not installed any debugger extension: * `SELECT * FROM pg_extension` shows no debugger-related extensions * `SELECT proname FROM pg_proc WHERE proname LIKE '%pldbg%'` returns no rows * `SELECT * FROM pg_available_extensions WHERE name LIKE '%debug%'` returns no rows However, `SHOW shared_preload_libraries` returns: ``` pg_stat_statements, pgaudit, plpgsql, plpgsql_check, pg_cron, pg_net, pgsodium, timescaledb, auto_explain, pg_tle, plan_filter, supabase_vault ``` The error references `pldbgapi2`, which is part of the PL/pgSQL debugger i…