where agg_signature is:
Description
stores a comment about a database object. Only one comment string is stored for each object. To remove a comment, write NULL
in place of the text string. Comments are automatically dropped when the object is dropped.
For most kinds of object, only the object’s owner can set the comment. Roles don’t have owners, so the rule for COMMENT ON ROLE
is that you must be superuser to comment on a superuser role, or have the CREATEROLE
privilege to comment on non-superuser roles. Of course, a superuser can comment on anything.
Comments can be easily retrieved with the psql meta-commands \dd
, \d+
, and \l+
. Other user interfaces to retrieve comments can be built atop the same built-in functions that psql uses, namely obj_description
, , and shobj_description
.
object_name
relation_name.column_name
agg_name
constraint_name
func_name
operator_name
rule_name
trigger_name
The name of the object to be commented. Names of tables, aggregates, collations, conversions, domains, foreign tables, functions, indexes, operators, operator classes, operator families, sequences, text search objects, types, views, and materialized views can be schema-qualified. When commenting on a column, relation_name must refer to a table, view, materialized view, composite type, or foreign table.
source_type
The name of the source data type of the cast.
target_type
The name of the target data type of the cast.
argmode
The mode of a function or aggregate argument: either IN
, OUT
, INOUT
, or VARIADIC
. If omitted, the default is IN
. Note that COMMENT
does not actually pay any attention to arguments, since only the input arguments are needed to determine the function’s identity. So it is sufficient to list the IN
, INOUT
, and VARIADIC
arguments.
argname
The name of a function or aggregate argument. Note that COMMENT ON FUNCTION
does not actually pay any attention to argument names, since only the argument data types are needed to determine the function’s identity.
argtype
The data type of a function or aggregate argument.
large_object_oid
The OID of the large object.
Greenplum Database does not support the PostgreSQL for streaming user data that is stored in large-object structures.
left_type
right_type
The data type(s) of the operator’s arguments (optionally schema-qualified). Write NONE
for the missing argument of a prefix or postfix operator.
PROCEDURAL
This is a noise word.
text
The new comment, written as a string literal; or NULL
to drop the comment.
Notes
There is presently no security mechanism for viewing comments: any user connected to a database can see all the comments for objects in that database. For shared objects such as databases, roles, and tablespaces, comments are stored globally so any user connected to any database in the cluster can see all the comments for shared objects. Therefore, do not put security-critical information in comments.
Attach a comment to the table mytable
:
Remove it again:
Some more examples:
Compatibility
There is no statement in the SQL standard.