This was only mentioned in the description of the text/label, which
are marked as being in quotes in the synopsis, which can cause
confusion (as witnessed on IRC).
Also separate the literal and NULL cases in the parameter list, per
suggestion from Tom Lane.
Also add an example of dropping a security label.
Dagfinn Ilmari Mannsåker, with some tweaks by me
Discussion: https://postgr.es/m/
[email protected]
TRIGGER trigger_name ON table_name |
TYPE object_name |
VIEW object_name
-} IS 'text'
+} IS { string_literal | NULL }
where aggregate_signature is:
- text
+ string_literal
- The new comment, written as a string literal; or NULL
- to drop the comment.
+ The new comment contents, written as a string literal.
+
+
+
+
+
+ NULL
+
+ Write NULL to drop the comment.
TABLESPACE object_name |
TYPE object_name |
VIEW object_name
-} IS 'label'
+} IS { string_literal | NULL }
where aggregate_signature is:
- label
+ string_literal
- The new security label, written as a string literal; or NULL
- to drop the security label.
+ The new setting of the security label, written as a string literal.
+
+
+
+
+
+ NULL
+
+ Write NULL to drop the security label.
Examples
- The following example shows how the security label of a table might
- be changed.
+ 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;
+
+