affected types of objects.
- You must own the aggregate function to use ALTER AGGREGATE>;
- except for ALTER AGGREGATE OWNER>, which may only be executed by
- a superuser.
+ You must own the aggregate function to use ALTER AGGREGATE>.
To change the schema of an aggregate function, you must also have
CREATE privilege on the new schema.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role, and that role must have CREATE privilege on
+ the aggregate function's schema. (These restrictions enforce that altering
+ the owner doesn't do anything you couldn't do by dropping and recreating
+ the aggregate function. However, a superuser can alter ownership of any
+ aggregate function anyway.)
ALTER CONVERSION changes the definition of a
conversion.
+
+ You must own the conversion to use ALTER CONVERSION>.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role, and that role must have CREATE privilege on
+ the conversion's schema. (These restrictions enforce that altering the
+ owner doesn't do anything you couldn't do by dropping and recreating the
+ conversion. However, a superuser can alter ownership of any conversion
+ anyway.)
+
newowner
- The new owner of the conversion. To change the owner of a conversion,
- you must be a superuser.
+ The new owner of the conversion.
- The fifth form changes the owner of the database. Only a superuser
- can change the database's owner.
+ The fifth form changes the owner of the database.
+ To alter the owner, you must own the database and also be a direct or
+ indirect member of the new owning role, and you must have the
+ CREATEDB privilege.
+ (Note that superusers have all these privileges automatically.)
- You must own the domain to use ALTER DOMAIN>; except for
- ALTER DOMAIN OWNER>, which may only be executed by a superuser.
- To change a domain's schema, you must also have CREATE>
- privilege on the new schema.
+ You must own the domain to use ALTER DOMAIN>.
+ To change the schema of a domain, you must also have
+ CREATE privilege on the new schema.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role, and that role must have CREATE privilege on
+ the domain's schema. (These restrictions enforce that altering the owner
+ doesn't do anything you couldn't do by dropping and recreating the domain.
+ However, a superuser can alter ownership of any domain anyway.)
- You must own the function to use ALTER FUNCTION>; except for
- ALTER FUNCTION OWNER>, which may only be executed by a superuser.
+ You must own the function to use ALTER FUNCTION>.
To change a function's schema, you must also have CREATE>
privilege on the new schema.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role, and that role must have CREATE privilege on
+ the function's schema. (These restrictions enforce that altering the owner
+ doesn't do anything you couldn't do by dropping and recreating the function.
+ However, a superuser can alter ownership of any function anyway.)
ALTER OPERATOR CLASS changes the definition of
an operator class.
+
+ You must own the operator class to use ALTER OPERATOR CLASS>.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role, and that role must have CREATE privilege on
+ the operator class's schema. (These restrictions enforce that altering the
+ owner doesn't do anything you couldn't do by dropping and recreating the
+ operator class. However, a superuser can alter ownership of any operator
+ class anyway.)
+
The new owner of the operator class.
- You must be a superuser to change the owner of an operator class.
an operator. The only currently available functionality is to change the
owner of the operator.
+
+ You must own the operator to use ALTER OPERATOR>.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role, and that role must have CREATE privilege on
+ the operator's schema. (These restrictions enforce that altering the owner
+ doesn't do anything you couldn't do by dropping and recreating the operator.
+ However, a superuser can alter ownership of any operator anyway.)
+
The new owner of the operator.
- You must be a superuser to change the owner of an operator.
ALTER SCHEMA changes the definition of a schema.
- To rename a schema you must own the schema and have the privilege
- CREATE for the database. To change the owner
- of a schema, you must be a superuser.
+
+
+ You must own the schema to use ALTER SCHEMA>.
+ To rename a schema you must also have the
+ CREATE privilege for the database.
+ To alter the owner, you must also be a direct or
+ indirect member of the new owning role, and you must have the
+ CREATE privilege for the database.
+ (Note that superusers have all these privileges automatically.)
ALTER TABLESPACE changes the definition of
a tablespace.
+
+ You must own the tablespace to use ALTER TABLESPACE>.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role.
+ (Note that superusers have these privileges automatically.)
+
The new owner of the tablespace.
- You must be a superuser to change the owner of a tablespace.
The only currently available capabilities are changing the owner and schema
of a type.
+
+ You must own the type to use ALTER TYPE>.
+ To change the schema of a type, you must also have
+ CREATE privilege on the new schema.
+ To alter the owner, you must also be a direct or indirect member of the new
+ owning role, and that role must have CREATE privilege on
+ the type's schema. (These restrictions enforce that altering the owner
+ doesn't do anything you couldn't do by dropping and recreating the type.
+ However, a superuser can alter ownership of any type anyway.)
+
The user name of the new owner of the type.
- You must be a superuser to change a type's owner.
new_schema
- The new schema for the type. To move a
- type to a new schema, you must be the owner of the
- type and have CREATE> privilege on the new schema.
+ The new schema for the type.