ALTER MATERIALIZED VIEW

    Description

    changes various auxiliary properties of an existing materialized view.

    You must own the materialized view to use ALTER MATERIALIZED VIEW. To change a materialized 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 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 DEPENDS ON EXTENSION form marks the materialized view as dependent on an extension, such that the materialized view will automatically be dropped if the extension is dropped.

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

    name

    The name (optionally schema-qualified) of an existing materialized view.

    Name of a new or existing column.

    extension_name

    The name of the extension that the materialized view is to depend on.

    new_column_name

    New name for an existing column.

    new_owner

    The new name for the materialized view.

    new_schema

    The new schema for the materialized view.

    Examples

    To rename the materialized view foo to bar:

    1. ALTER MATERIALIZED VIEW foo RENAME TO bar;

    ALTER MATERIALIZED VIEW is a PostgreSQL extension.

    See Also