ALTER SCHEMA
ALTER SCHEMA — change the definition of a schema
Synopsis
ALTER SCHEMAnameRENAME TOnew_nameALTER SCHEMAnameOWNER TO {new_owner| CURRENT_ROLE | CURRENT_USER | SESSION_USER } ALTER SCHEMAnameSECURITY OFFICER TOnew_security_officerALTER SCHEMAnameRESET SECURITY OFFICER
Description
ALTER SCHEMA changes the definition of a schema.
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 be able to SET ROLE to the new owning role, and that role must have the CREATE privilege for the database. (Note that superusers have all these privileges automatically.)
The SECURITY OFFICER clause sets the security officer of the schema, while the RESET SECURITY OFFICER clause resets the security officer. When you set the security officer, the schema becomes the vault schema.
Setting a security officer requires the enable_security_officer configuration parameter to be enabled. Once the security officer is set, the schema continues to operate with enhanced security even if this parameter is later disabled. Resetting the security officer remains possible regardless of this parameter.
Parameters
nameThe name of an existing schema.
new_nameThe new name of the schema. The new name cannot begin with
pg_, as such names are reserved for system schemas.new_ownerThe new owner of the schema.
new_security_officerThe new security officer of the schema.
Compatibility
There is no ALTER SCHEMA statement in the SQL standard.