Re: information_schema.columns.character_octet_length unavailable if no access to pg_database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien Meghazi <amigrave(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: information_schema.columns.character_octet_length unavailable if no access to pg_database
Date: 2017-08-03 13:53:14
Message-ID: 5705.1501768394@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Fabien Meghazi <amigrave(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message rbiro 2017-08-03 14:11:47 BUG #14770: postgres_fdw assumes foreign table is in postgres
Previous Message Krystian Szladewski 2017-08-03 12:35:57 "could not open relation with OID XXX" when using recreated index in sql function