| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Cc: | KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] SE-PgSQL/lite rev.2163 |
| Date: | 2009-07-16 02:11:23 |
| Message-ID: | 603c8f070907151911w4f74da08u7de5a182cd6da16a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/7/14 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>:
> On the other hand, db_schema class was designed as an analogy to
> directoty in filesystems. SELinux defines several permissions on
> "dir" object class, such as "add_name", "remove_name" and "search".
I think that's a bad analogy and you need to make the permission names
match the way PostgreSQL handles schema permissions generally.
There's only so many times and ways to says this...
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2009-07-16 02:38:02 | Re: [PATCH] SE-PgSQL/lite rev.2163 |
| Previous Message | Tom Lane | 2009-07-16 02:03:05 | Re: [GENERAL] pg_migrator not setting values of sequences? |