Re: Changing a schema's name with function1 calling function2 - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Changing a schema's name with function1 calling function2
Date
Msg-id c2954d6e-a739-431e-829a-02919d58b48b@aklaver.com
Whole thread Raw
In response to Re: Changing a schema's name with function1 calling function2  (Kirk Wolak <wolakk@gmail.com>)
Responses Re: Re: Changing a schema's name with function1 calling function2
List pgsql-general
On 12/26/23 22:41, Kirk Wolak wrote:
> On Mon, Dec 25, 2023 at 1:47 PM Christophe Pettus <xof@thebuild.com 
> <mailto:xof@thebuild.com>> wrote:
> 
> 
> 
>      > On Dec 25, 2023, at 10:44, Adrian Klaver
>     <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>      > Functions with same name in different schemas would need to be
>     dealt with.
> 
>     I think that's the primary use-case (at least, it would be for me),
>     and I don't see a convenient way of doing that.  Even a "get OID of
>     current function" function would be useful here.
> 
> And Pavel Already Created it:
> GET DIAGNOSTIC PID = PG_ROUTINE_OID ;

To be clear the above is for Postgres 16+ and for the plpgsql language only.

> 
> If I understand the issue correctly.
> 
> Kirk Out!

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Kaushik Iska
Date:
Subject: Re: Intermittent Issue with WAL Segment Removal in Logical Replication
Next
From: Clemens Eisserer
Date:
Subject: Re: Query crash with 15.5 on debian bookworm/armv8