| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Cc: | 张元超 <zhangyuanchao(at)highgo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: One question about security label command |
| Date: | 2015-03-09 14:55:57 |
| Message-ID: | CA+TgmoY9CEDu0mTLyHU-jzBuDKegspJGip=aE1hOTumDAzYYnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 3, 2015 at 5:01 AM, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> wrote:
> From standpoint of SQL syntax, yep, SECURITY LABEL command support
> the object types below, however, it fully depends on security label
> provider; sepgsql.so in this case.
> At this moment, it supports database, schema, function, tables and
> column are supported by sepgsql. So, it is expected behavior.
If the core system supports labels on other object types and sepgsql
does not, it should give a better error for those cases, like:
ERROR: sepgsql provider does not support labels on roles
Errors like "ERROR: unsupported object type: 1260" are a good way to
report a failure that is never expected to happen, but they shouldn't
be used as user-facing error messages.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-03-09 14:59:46 | Re: pg_rewind in contrib |
| Previous Message | Abhijit Menon-Sen | 2015-03-09 14:43:59 | Re: MD5 authentication needs help -SCRAM |