| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-02-05 02:58:33 | source download link in installation instructions |
| Previous Message | Bruce Momjian | 2013-01-25 20:54:28 | Re: Manual Entries of commit_delay and commit_siblings are not complete. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltán Böszörményi | 2013-01-31 21:12:01 | Re: Strange Windows problem, lock_timeout test request |
| Previous Message | Pavel Stehule | 2013-01-31 20:43:24 | Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used |