| From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
|---|---|
| To: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Cc: | robertmhaas(at)gmail(dot)com, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, kaigai(at)kaigai(dot)gr(dot)jp |
| Subject: | Re: security hooks on object creation |
| Date: | 2010-11-09 11:34:51 |
| Message-ID: | AANLkTimvTd4Xj1pYd5Ap5FRwsGX92aSsxLO5rt-VOU7K@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/11/9 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>:
> The attached patch provides plugin modules a hook just after object
> creation time. In typical use cases, it enables to assign default
> security labels on object creation by the external security providers.
It looks like "DDL Trigger" on other database products.
Do we need to consider both security hooks and DDL triggers now?
Or, is it enough to design DLL triggers after the hooks are merged?
Low-level hooks might be better for security providers because
SQL-level triggers could be uninstall by superusers.
--
Itagaki Takahiro
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-11-09 11:34:56 | Re: Hot Standby b-tree delete records review |
| Previous Message | Jakub Ouhrabka | 2010-11-09 11:16:31 | Re: Avoid memory leaks during ANALYZE's compute_index_stats() ? |