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-11-29 13:12:37
Message-ID: CAFj8pRDEP3u+gNmmvtps26tSxBjV93mDxxCzYrOi3cuCOKW=vQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi

út 29. 11. 2022 v 13:49 odesílatel shashidhar Reddy <
shashidharreddy001(at)gmail(dot)com> napsal:

> Hello,
>
> Recently we have upgraded postgres from version 12 to 13 and upgraded plpgsql_check
> to the latest version but after upgrade when calling the below function
> causing postgres restart .
>
> CREATE OR REPLACE FUNCTION pro.po_check(
> )
> RETURNS void
> LANGUAGE 'plpgsql'
> COST 100
> VOLATILE SECURITY DEFINER PARALLEL UNSAFE
> AS $BODY$
> DECLARE
> BEGIN
>
> PERFORM p.oid, n.nspname, p.proname, plpgsql_check_function(p.oid)
> FROM pg_catalog.pg_namespace n
> JOIN pg_catalog.pg_proc p ON pronamespace = n.oid
> JOIN pg_catalog.pg_language l ON p.prolang = l.oid
> WHERE l.lanname = 'plpgsql' AND p.prorettype <> 2279
> and upper(n.nspname) like upper('Pro');
>
> END;
> $BODY$;
>
> and the error in syslogs shows
> kernel: [93631.415790] postgres[86383]: segfault at 80 ip 00007f07f3e3eefd
> sp 00007fffcf1db500 error 4 in plpgsql_check.so[7f07f3e2e000+34000]
>

it can be a bug in plpgsql_check. But I am not able to fix it without some
information. Can you send the reproducer (minimal example of your code,
that reproduce this error)?

Regards

Pavel

>
> --
> Shashidhar
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message shashidhar Reddy 2022-11-29 13:49:32 Re: plpgsql_check_function issue after upgrade
Previous Message shashidhar Reddy 2022-11-29 12:48:35 plpgsql_check_function issue after upgrade