Re: [BUGS] information_schema.columns.character_octet_length unavailable if no access to pg_database - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] information_schema.columns.character_octet_length unavailable if no access to pg_database
Date
Msg-id 5705.1501768394@sss.pgh.pa.us
Whole thread Raw
In response to [BUGS] information_schema.columns.character_octet_length unavailable if noaccess to pg_database  (Fabien Meghazi <amigrave@gmail.com>)
List pgsql-bugs
Fabien Meghazi <amigrave@gmail.com> writes:
> On any database, when the pg_database access is restraint for standard
> users:
>     psql> REVOKE ALL ON pg_database FROM public;
> it not possible anymore to query the field character_octet_length from the
> view information_schema.columns:

It's pretty hard to get excited about that --- it seems like it's going
to be about the least of your problems, if you start revoking public read
permissions on random system catalogs.  Postgres isn't really designed
with that sort of change in mind.
        regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Krystian Szladewski
Date:
Subject: [BUGS] "could not open relation with OID XXX" when using recreated index insql function
Next
From: rbiro@interfacefinancial.com
Date:
Subject: [BUGS] BUG #14770: postgres_fdw assumes foreign table is in postgres