ALTER VIEW
ALTER VIEW — change the definition of a view
Synopsis
ALTER VIEW [ IF EXISTS ]nameALTER [ COLUMN ]column_nameSET DEFAULTexpressionALTER VIEW [ IF EXISTS ]nameALTER [ COLUMN ]column_nameDROP DEFAULT ALTER VIEW [ IF EXISTS ]nameOWNER TO {new_owner| CURRENT_ROLE | CURRENT_USER | SESSION_USER } ALTER VIEW [ IF EXISTS ]nameRENAME [ COLUMN ]column_nameTOnew_column_nameALTER VIEW [ IF EXISTS ]nameRENAME TOnew_nameALTER VIEW [ IF EXISTS ]nameSET SCHEMAnew_schemaALTER VIEW [ IF EXISTS ]nameSET (view_option_name[=view_option_value] [, ... ] ) ALTER VIEW [ IF EXISTS ]nameRESET (view_option_name[, ... ] )
Description
ALTER VIEW changes various auxiliary properties of a view. (If you want to modify the view's defining query, use CREATE OR REPLACE VIEW.)
You must own the view to use ALTER VIEW. To change a view'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 view's schema. (These restrictions enforce that altering the owner doesn't do anything you couldn't do by dropping and recreating the view. However, a superuser can alter ownership of any view anyway.)
Parameters
nameThe name (optionally schema-qualified) of an existing view.
column_nameName of an existing column.
new_column_nameNew name for an existing column.
IF EXISTSDo not throw an error if the view does not exist. A notice is issued in this case.
SET/DROP DEFAULTThese forms set or remove the default value for a column. A view column's default value is substituted into any
INSERTorUPDATEcommand whose target is the view, before applying any rules or triggers for the view. The view's default will therefore take precedence over any default values from underlying relations.new_ownerThe user name of the new owner of the view.
new_nameThe new name for the view.
new_schemaThe new schema for the view.
SET (view_option_name[=view_option_value] [, ... ] )RESET (view_option_name[, ... ] )Sets or resets a view option. Currently supported options are:
check_option(enum)Changes the check option of the view. The value must be
localorcascaded.security_barrier(boolean)Changes the security-barrier property of the view. The value must be a Boolean value, such as
trueorfalse.security_invoker(boolean)Changes the security-invoker property of the view. The value must be a Boolean value, such as
trueorfalse.
Notes
For historical reasons, ALTER TABLE can be used with views too; but the only variants of ALTER TABLE that are allowed with views are equivalent to the ones shown above.
Examples
To rename the view foo to bar:
ALTER VIEW foo RENAME TO bar;
To attach a default column value to an updatable view:
CREATE TABLE base_table (id int, ts timestamptz); CREATE VIEW a_view AS SELECT * FROM base_table; ALTER VIEW a_view ALTER COLUMN ts SET DEFAULT now(); INSERT INTO base_table(id) VALUES(1); -- ts will receive a NULL INSERT INTO a_view(id) VALUES(2); -- ts will receive the current time
Compatibility
ALTER VIEW is a Postgres Pro extension of the SQL standard.