Hi Hackers,
Attached is the patch for RM4123, where debugger doesn't work if the search
path is set other than public(where the debugger extension is installed).
Now the schema public is appended to the existing search path and it will
now work no matter what the search path is.
I've also renamed
Hi Akshay,
On Tue, Aug 11, 2020 at 12:13 PM Akshay Joshi
wrote:
> Hi Aditya
>
> On Thu, Aug 6, 2020 at 4:48 PM Aditya Toshniwal <
> aditya.toshni...@enterprisedb.com> wrote:
>
>> Hi Dave/Team,
>>
>> I've been working on an issue to make debugger work no matter what the
>> search patch is set. I'
Hi Aditya
On Thu, Aug 6, 2020 at 4:48 PM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> 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 qual
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,
