On Monday, October 5, 2020, James B. Byrne <byrn...@harte-lyne.ca> wrote:
>
> idempiere(5432)=# alter role "idempiere_dbadmin" set search_path =
> 'adempiere,
> public';
> ALTER ROLE
> idempiere(5432)=# select current_schemas(true);
> current_schemas
> -----------------
> {pg_catalog}
> (1 row)
>
> This does not look like the ALTER statement had any effect. Am I missing
> a step?
>
Whenever the role subsequently starts a new session, the specified value
becomes the session default, overriding whatever setting is present in
postgresql.conf or has been received from the postgres command line. This
only happens at login time; executing SET ROLE
<https://www.postgresql.org/docs/13/sql-set-role.html> or SET SESSION
AUTHORIZATION
<https://www.postgresql.org/docs/13/sql-set-session-authorization.html> does
not cause new configuration values to be set.
https://www.postgresql.org/docs/13/sql-alterrole.html
David J.
