On Mon, Jan 24, 2022 at 11:19 AM Ganesh Korde <ganeshakorde@gmail.com> wrote:
> On Mon, 24 Jan 2022, 3:22 pm Dominique Devienne, <ddevienne@gmail.com> wrote:
>> Is there any way to achieve that, beside our current `SET search_path` workaround?
> This might help.
> Alter user <user name> SET search_path TO myschema,public;
> No need to set search_path every time.
Hi. Not really, no, I'm afraid.
I'm in charge and control the app's schemas, not the LOGIN USERs using
those schemas.
I.e. my triggers shouldn't have to rely on the session's search_path
at all, and nor how that search_path is set.
Also, the schema(s) to access are dynamic, and some clients don't set
a search_path at all.
My triggers shouldn't stop working when there's no search_path (i.e.
only pg_catalog and pg_temp are implicitly resolved).