Re: plpgsql_check_function issue after upgrade

From: shashidhar Reddy <shashidharreddy001(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: plpgsql_check_function issue after upgrade
Date: 2022-12-06 13:52:50
Message-ID: CAH=zU4t0SsyEzoOS_TqAYKRByR2G4-msmOUxHGWoEVdhvq+dRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 6 Dec, 2022, 4:17 pm Pavel Stehule, <pavel(dot)stehule(at)gmail(dot)com> wrote:

> Hi
>
> for record - the problem was probably in using plpgsql_check together with
> PL debugger (plugin_debugger). Both extensions use the PLpgSQL DBG API, but
> this API is not designed to be used by more extensions. plpgsql_check has
> implemented some workaround, but it should be loaded last if this
> workaround should work. Older versions of plpgsq_check (without profiler)
> didn't use DBG API.
>
> https://github.com/okbob/plpgsql_check#using-with-plugin_debugger
>

I am loading the plpgsql_chect last after loading other extensions.

Looks like it is working for now, but need more time to check on it.

>
> Regards
>
> Pavel
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Loftis 2022-12-06 15:03:34 Re: postgres large database backup
Previous Message Mateusz Henicz 2022-12-06 12:43:26 Re: Monitoring-only role