| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jan Behrens <jbe-mlist(at)magnetkern(dot)de> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: search_path for PL/pgSQL functions partially cached? |
| Date: | 2024-12-28 05:34:46 |
| Message-ID: | CAFj8pRC70kmnPKhNCNJ9y+v3gRBTEUTpWs9kbTQL_c3i58QnEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi
> Maybe not many people run into these issues because schemas and
> functions aren't used as often in combination?
>
I think schema and functions are common combinations. But when people have
objects with the same name, then they are careful to be sure, so objects
have really identical structure.
Using different types in these objects is very rare. And because Postgres
doesn't support it well, experienced developers don't use it. Similar
issues can do some issues after an stored procedures update, because can
require session reset. Or when you need it, you can use a much more dynamic
type like record.
> Kind Regards
> Jan Behrens
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2024-12-28 17:49:27 | Re: Updated Fedora 40 and Fedora 41 RPM packages of Pgpool-II 4.5.5 in the repo |
| Previous Message | Jan Behrens | 2024-12-27 23:40:09 | Re: search_path for PL/pgSQL functions partially cached? |