Re: [v9.2] Object access hooks with arguments support (v1)
От | Robert Haas |
---|---|
Тема | Re: [v9.2] Object access hooks with arguments support (v1) |
Дата | |
Msg-id | CA+TgmobfQ+Um9O28jrvARMQNf11ZNSCYPJkkbCwmw8Bcq3xSqA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [v9.2] Object access hooks with arguments support (v1) (Kohei KaiGai <kaigai@kaigai.gr.jp>) |
Ответы |
Re: [v9.2] Object access hooks with arguments support (v1)
|
Список | pgsql-hackers |
On Mon, Nov 7, 2011 at 12:20 PM, Kohei KaiGai <kaigai@kaigai.gr.jp> wrote: > If sepgsql would apply permission checks db_procedure:{install} on the > OAT_POST_CREATE hook based on the funcion-oid within new entry of > system catalog, we can relocate OAT_PREP_CREATE hook more conceptually > right place, such as just after the pg_namespace_aclcheck() of DefineType(). > On the other hand, we may need to answer why these information are NOT > delivered on the OAT_PREP_CREATE hook without knowledge of sepgsql > internal. I'm having a hard time understanding this. Can you strip this patch down so it just applies to a single object type (tables, maybe, or functions, or whatever you like) and then submit the corresponding sepgsql changes with it? Just as a demo patch, so I can understand where you're trying to go with this. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: