Re: UUID generation problem
| От | David G. Johnston |
|---|---|
| Тема | Re: UUID generation problem |
| Дата | |
| Msg-id | CAKFQuwbohUn4PNmOtSvX7o9F8We3ZgL6A=NU8ePc=Vd6S=4Y-w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: UUID generation problem ("James B. Byrne" <byrnejb@harte-lyne.ca>) |
| Ответы |
[SOLVED] Re: UUID generation problem
|
| Список | 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 по дате отправления: