NAME
SECURITY_LABEL - define or change a security label applied to an object
SYNOPSIS
SECURITY LABEL [ FOR \nprovider\n ] ON
{
\n
TABLE \nobject_name\n |
\n
COLUMN \ntable_name\n.\ncolumn_name\n |
\n
AGGREGATE \naggregate_name\n ( \naggregate_signature\n ) |
\n
DATABASE \nobject_name\n |
\n
DOMAIN \nobject_name\n |
\n
EVENT TRIGGER \nobject_name\n |
\n
FOREIGN TABLE \nobject_name\n |
\n
FUNCTION \nfunction_name\n [ ( [ [ \nargmode\n ] [ \nargname\n ] \nargtype\n [, ...] ] ) ] |
\n
LARGE OBJECT \nlarge_object_oid\n |
\n
MATERIALIZED VIEW \nobject_name\n |
\n
[ PROCEDURAL ] LANGUAGE \nobject_name\n |
\n
PROCEDURE \nprocedure_name\n [ ( [ [ \nargmode\n ] [ \nargname\n ] \nargtype\n [, ...] ] ) ] |
\n
PUBLICATION \nobject_name\n |
\n
ROLE \nobject_name\n |
\n
ROUTINE \nroutine_name\n [ ( [ [ \nargmode\n ] [ \nargname\n ] \nargtype\n [, ...] ] ) ] |
\n
SCHEMA \nobject_name\n |
\n
SEQUENCE \nobject_name\n |
\n
SUBSCRIPTION \nobject_name\n |
\n
TABLESPACE \nobject_name\n |
\n
TYPE \nobject_name\n |
\n
VIEW \nobject_name\n
} IS { \nstring_literal\n | NULL }
where \naggregate_signature\n is:
* |
[ \nargmode\n ] [ \nargname\n ] \nargtype\n [ , ... ] |
[ [ \nargmode\n ] [ \nargname\n ] \nargtype\n [ , ... ] ] ORDER BY [ \nargmode\n ] [ \nargname\n ] \nargtype\n [ , ... ]DESCRIPTION
SECURITY LABEL applies a security label to a database object. An arbitrary number of security labels, one per label provider, can be associated with a given database object. Label providers are loadable modules which register themselves by using the function register_label_provider.
register_label_provider is not an SQL function; it can only be called from C code loaded into the backend.
The label provider determines whether a given label is valid and whether it is permissible to assign that label to a given object. The meaning of a given label is likewise at the discretion of the label provider. PostgreSQL places no restrictions on whether or how a label provider must interpret security labels; it merely provides a mechanism for storing them. In practice, this facility is intended to allow integration with label-based mandatory access control (MAC) systems such as SELinux. Such systems make all access control decisions based on object labels, rather than traditional discretionary access control (DAC) concepts such as users and groups.
You must own the database object to use SECURITY LABEL.
PARAMETERS
object_name table_name.column_name aggregate_name function_name procedure_name routine_name
provider
argmode
argname
argtype
large_object_oid
PROCEDURAL
string_literal
NULL
EXAMPLES
The following example shows how the security label of a table could be set or changed:
SECURITY LABEL FOR selinux ON TABLE mytable IS 'system_u:object_r:sepgsql_table_t:s0';To remove the label:
SECURITY LABEL FOR selinux ON TABLE mytable IS NULL;COMPATIBILITY
There is no SECURITY LABEL command in the SQL standard.
SEE ALSO
sepgsql, src/test/modules/dummy_seclabel