I did investigate this issue and the problem is pg_has_role function.
Take a look at information_schema.schemata definition below
SELECT (current_database ()) ::information_schema.sql_identifier AS
catalog_name
, (n.nspname) ::information_schema.sql_identifier AS schema_name
, (u.rolname) ::information_schema.sql_identifier AS schema_owner
, (NULL::character VARYING) ::information_schema.sql_identifier AS
default_character_set_catalog
, (NULL::character VARYING) ::information_schema.sql_identifier AS
default_character_set_schema
, (NULL::character VARYING) ::information_schema.sql_identifier AS
default_character_set_name
, (NULL::character VARYING) ::information_schema.character_data AS
sql_path
FROM pg_namespace n
, pg_authid u
WHERE ((n.nspowner = u.oid) AND pg_has_role (n.nspowner, 'USAGE'::text));
--
View this message in context: http://postgresql.1045698.n5.nabble.com/problems-viewing-information-schema-schemata-tp4639500p4640939.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
