Skip site navigation (1) Skip section navigation (2)

Re: Privileges for INFORMATION_SCHEMA.SCHEMATA (was Re: Small clarification in "34.41. schemata")

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ian Lawrence Barwick <barwick(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Privileges for INFORMATION_SCHEMA.SCHEMATA (was Re: Small clarification in "34.41. schemata")
Date: 2013-01-31 20:49:36
Message-ID: 510AD8E0.9020005@gmx.net (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackers
On 1/9/13 8:56 PM, Tom Lane wrote:
> However, it seems to me that this behavior is actually wrong for our
> purposes, as it represents a too-literal reading of the spec.  The SQL
> standard has no concept of privileges on schemas, only ownership.
> We do have privileges on schemas, so it seems to me that the consistent
> thing would be for this view to show any schema that you either own or
> have some privilege on.  That is the test should be more like 
> 
> 	pg_has_role(n.nspowner, 'USAGE')
> 	OR has_schema_privilege(n.oid, 'CREATE, USAGE')
> 
> As things stand, a non-superuser won't see "public", "pg_catalog",
> nor even "information_schema" itself in this view, which seems a
> tad silly.

I agree it would make sense to change this.



In response to

Responses

pgsql-docs by date

Next:From: Peter EisentrautDate: 2013-02-05 02:58:33
Subject: source download link in installation instructions
Previous:From: Bruce MomjianDate: 2013-01-25 20:54:28
Subject: Re: Manual Entries of commit_delay and commit_siblings are not complete.

pgsql-hackers by date

Next:From: Zoltán BöszörményiDate: 2013-01-31 21:12:01
Subject: Re: Strange Windows problem, lock_timeout test request
Previous:From: Pavel StehuleDate: 2013-01-31 20:43:24
Subject: Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group