I have a private schema where I have declared a table (let's say table user profile which references auth.users), a trigger function and a trigger on auth.users

The interesting thing is that regardless of whether I add the new schema to the extra search path, the following things happen:

1) Any views I declare in the public schema which reference the private table (e.g. in a JOIN clause) work just fine even if I don't qualify them with the schema name. I don't understand why that does works even when I have NOT specified the private schema in the extra search path

2) Any triggers which do NOT specifically qualify the functions and/or tables in the private schema fail, even if I've added the private schema to the extra search path

I see that the extra search path does take effect for functions in the public schema - it is possible that my problem is that the trigger functions themselves are defined in the private schema and so the extra search path does NOT have an effect on them?

I tried moving my triggers to the public schema and there was no change - I guess I will open a discussion on GitHub with a suggestion to allow extra serach paths for triggers