Thread: pgsql: sepgsql: Support for new post-ALTER access hook.

pgsql: sepgsql: Support for new post-ALTER access hook.

From
Robert Haas
Date:
sepgsql: Support for new post-ALTER access hook.

KaiGai Kohei

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/1cea9bbb21e9e90dc7085ce605d9160e7161fa58

Modified Files
--------------
contrib/sepgsql/database.c         |   27 +++++
contrib/sepgsql/expected/alter.out |  192 ++++++++++++++++++++++++++++++++++++
contrib/sepgsql/expected/ddl.out   |    9 ++
contrib/sepgsql/hooks.c            |   48 +++++++++
contrib/sepgsql/proc.c             |   90 ++++++++++++++++-
contrib/sepgsql/relation.c         |   91 ++++++++++++++++--
contrib/sepgsql/schema.c           |   51 ++++++++++
contrib/sepgsql/sepgsql.h          |    7 ++
contrib/sepgsql/sql/alter.sql      |  136 +++++++++++++++++++++++++
contrib/sepgsql/sql/ddl.sql        |    6 +
contrib/sepgsql/test_sepgsql       |   27 +++++-
doc/src/sgml/sepgsql.sgml          |   22 ++++-
12 files changed, 693 insertions(+), 13 deletions(-)


Re: pgsql: sepgsql: Support for new post-ALTER access hook.

From
Thom Brown
Date:
On 27 March 2013 12:33, Robert Haas <rhaas@postgresql.org> wrote:
> sepgsql: Support for new post-ALTER access hook.

I notice that due to commit bc5334d8 I can't actually build the docs
at the moment.

But I think the language here definitely needs improving:

"On CREATE FUNCTION, install permission will be checked if leakproof
attribute was given, not only create on the new function. This
permission will be also checked when user tries to turn on leakproof
attribute using ALTER FUNCTION command, with setattr permission on the
function being altered."

And are the literals there capitalised when rendered?  If not, could I
suggest they be capitalised in the SGML?

also:

s/for each object types/for each object type/

--
Thom