Re: security hook on table creation

2010/9/29 KaiGai Kohei <kaigai@ak.jp.nec.com>:
> In addition, I want to give these entrypoints its name which
> represents an appropriate purpose of the hook, rather than
> a uniformed one.

It sounds like you're proposing to create a vast number of hooks
rather than just one.  If we have ~20 object types in the system,
that's 40 hooks just for create and drop, and then many more to handle
comment, alter (perhaps in various flavors), etc.  I'm pretty
unexcited about that.  The main hook function can always dispatch
internally if it so desires, but I don't see any benefit to forcing
people to write the code that way.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company