Re: CREATE EXTENSION forces an library initialization - is it bug?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: CREATE EXTENSION forces an library initialization - is it bug?
Date: 2023-09-29 18:19:22
Message-ID: CAFj8pRBhqZShQbUhZPj6UbbhNdtb+brU_QvUK_pv-Xoe-RoVAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pá 29. 9. 2023 v 20:14 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:

> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > I had to fix plpgsql_check issue
> > https://github.com/okbob/plpgsql_check/issues/155
>
> > The problem is in execution of _PG_init() in CREATE EXTENSION time.
>
> > It is a problem for any extension that uses plpgsql debug API, because it
> > is quietly activated.
>
> > Is it necessary?
>
> Yes, I think so. If the extension has any C functions, then when its
> script executes those CREATE FUNCTION commands then the underlying
> library will be loaded (so we can check that the library is loadable
> and the functions really exist). That's always happened and I do not
> think it is negotiable.
>

ok

thank you for info

>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2023-09-29 18:26:19 Re: Fix incorrect comment reference
Previous Message Tom Lane 2023-09-29 18:14:24 Re: CREATE EXTENSION forces an library initialization - is it bug?