Re: plpgsql_check_function issue after upgrade

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: shashidhar Reddy <shashidharreddy001(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 10:47:07
Message-ID: CAFj8pRAie0FbybFqqfrYDkQPs-SaNxkbv+cbud=BjgOVbm=aXg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Regards

Pavel

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Wiwwo Staff 2022-12-06 12:37:37 Monitoring-only role
Previous Message hvjunk 2022-12-06 04:44:15 Re: postgres large database backup