pgAdmin debugger failure when search_path set - Mailing list pgadmin-hackers

From Aditya Toshniwal
Subject pgAdmin debugger failure when search_path set
Date
Msg-id CAM9w-_=MfokguDFWvUyBFVQcs_n55Fk5DEodpDWfXiBGb_-Y9Q@mail.gmail.com
Whole thread Raw
Responses Re: pgAdmin debugger failure when search_path set
List pgadmin-hackers
Hi Dave/Team,

I've been working on an issue to make debugger work no matter what the search patch is set. I've managed to call the appropriate functions from pgAdmin using a schema qualified name with no issues. However, the internal calls in the function don't look schema qualified.
For instance,
I have two schemas "public" where the debugger is installed and "other" where my user defined function is. I set the search_path to "other" on the database. Calling plpgsql_oid_debug directly fails because of the search path set, but I can call the debugger functions with public.plpgsql_oid_debug, but it fails with:
ERROR: function pldbg_oid_debug(oid) does not exist LINE 1: SELECT pldbg_oid_debug($1) ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. QUERY: SELECT pldbg_oid_debug($1) CONTEXT: SQL function "plpgsql_oid_debug" during inlining

How to approach this ? It is inconvenient for users to remove their search_path to make debugger work.

--
Thanks,
Aditya Toshniwal
pgAdmin hacker | Sr. Software Engineer | edbpostgres.com
"Don't Complain about Heat, Plant a TREE"

pgadmin-hackers by date:

Previous
From: Murtuza Zabuawala
Date:
Subject: Re: [pgAdmin][RM5716] AJAX to generate the charts continues to fire after we disconnect the server
Next
From: Akshay Joshi
Date:
Subject: pgAdmin 4 commit: Fixed an issue where ajax call continues to fire even