Name

Synopsis

ALTER MATERIALIZED VIEW [ IF EXISTS ]nameaction [, ... ]ALTER MATERIALIZED VIEW [ IF EXISTS ]name    RENAME [ COLUMN ]column_name TOnew_column_nameALTER MATERIALIZED VIEW [ IF EXISTS ]name    RENAME TOnew_nameALTER MATERIALIZED VIEW [ IF EXISTS ]name    SET SCHEMAnew_schemaALTER MATERIALIZED VIEW ALL IN TABLESPACEname [ OWNED BYrole_name [, ... ] ]    SET TABLESPACEnew_tablespace [ NOWAIT ]whereaction is one of:    ALTER [ COLUMN ]column_name SET STATISTICSinteger    ALTER [ COLUMN ]column_name SET (attribute_option =value [, ... ] )    ALTER [ COLUMN ]column_name RESET (attribute_option [, ... ] )    ALTER [ COLUMN ]column_name SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }    CLUSTER ONindex_name    SET WITHOUT CLUSTER    SET (storage_parameter =value [, ... ] )    RESET (storage_parameter [, ... ] )    OWNER TOnew_owner    SET TABLESPACEnew_tablespace

Description

ALTER MATERIALIZED VIEW changes various auxiliary properties of an existing materialized view.

You must own the materialized view to useALTER MATERIALIZED VIEW. To change a materialized view's schema, you must also haveCREATE 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 haveCREATE privilege on the materialized view's schema. (These restrictions enforce that altering the owner doesn't do anything you couldn't do by dropping and recreating the materialized view. However, a superuser can alter ownership of any view anyway.)

The statement subforms and actions available forALTER MATERIALIZED VIEW are a subset of those available forALTER TABLE, and have the same meaning when used for materialized views. See the descriptions forALTER TABLE for details.

Parameters

Examples

To rename the materialized viewfoo tobar:

ALTER MATERIALIZED VIEW foo RENAME TO bar;

Compatibility

ALTER MATERIALIZED VIEW is aPostgreSQL extension.

See Also