I am new to this list, so I do not know if this has been reported
already (did not find anything regarding search_path in the issue tracker).
If you use pgadmin4 to alter the search_path for a role, all queries
that do not explicitly use a schema name with tables fail. Apparently,
pgadmin4 is treating a comma-separated list of schema names as a single
name, so, for example, "public, journal" is treated as a single schema
name of 'public, journal', not 'public' and 'journal'. One must manually
alter the role in SQL to correct it.
Bruce
Win 7/x64, postgres 9.6
Modify properties for a role.
Select Parameters tab.
Click +
Select search_path from list.
Enter comma-separated list for value.
Leave database blank.
Pgadmin4 generated SQL:
ALTER ROLE myrole
RESET search_path;
ALTER ROLE myrole
SET search_path TO 'public, journal';
(value should not be quoted)
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
