Re: UUID generation problem - Mailing list pgsql-general

From David G. Johnston
Subject Re: UUID generation problem
Date
Msg-id CAKFQuwbohUn4PNmOtSvX7o9F8We3ZgL6A=NU8ePc=Vd6S=4Y-w@mail.gmail.com
Whole thread Raw
In response to Re: UUID generation problem  ("James B. Byrne" <byrnejb@harte-lyne.ca>)
Responses [SOLVED] Re: UUID generation problem  ("James B. Byrne" <byrnejb@harte-lyne.ca>)
List pgsql-general
On Monday, October 5, 2020, James B. Byrne <byrnejb@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 or SET SESSION AUTHORIZATION does not cause new configuration values to be set.


David J.

pgsql-general by date:

Previous
From: "James B. Byrne"
Date:
Subject: Re: UUID generation problem
Next
From: Tatsuo Ishii
Date:
Subject: Re: 回复: May "PostgreSQL server side GB18030 character set support" reconsidered?