| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Kirk Wolak <wolakk(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | Wilma Wantren <wilma(dot)wantren(at)eclipso(dot)de>, "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Changing a schema's name with function1 calling function2 |
| Date: | 2023-12-27 15:40:55 |
| Message-ID: | c2954d6e-a739-431e-829a-02919d58b48b@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/26/23 22:41, Kirk Wolak wrote:
> On Mon, Dec 25, 2023 at 1:47 PM Christophe Pettus <xof(at)thebuild(dot)com
> <mailto:xof(at)thebuild(dot)com>> wrote:
>
>
>
> > On Dec 25, 2023, at 10:44, Adrian Klaver
> <adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clemens Eisserer | 2023-12-28 11:41:29 | Re: Query crash with 15.5 on debian bookworm/armv8 |
| Previous Message | Kaushik Iska | 2023-12-27 15:31:14 | Re: Intermittent Issue with WAL Segment Removal in Logical Replication |