ALTER_MATERIALIZED_VIEW(7pg17)

📦 version 17.11, in opensuse-leap 16.0

💅 NAME 💅

okay so bestie, you're in the PostgreSQL 17.11 documentation for ALTER MATERIALIZED VIEW(7) — the manual page ALTER_MATERIALIZED_VIEW — and it's literally about changing the definition of a materialized view. main character energy, no cap ✨

🎀 SYNOPSIS 🎀

ALTER MATERIALIZED VIEW [ IF EXISTS ] name
    action [, ... ]
ALTER MATERIALIZED VIEW name
    [ NO ] DEPENDS ON EXTENSION extension_name
ALTER MATERIALIZED VIEW [ IF EXISTS ] name
    RENAME [ COLUMN ] column_name TO new_column_name
ALTER MATERIALIZED VIEW [ IF EXISTS ] name
    RENAME TO new_name
ALTER MATERIALIZED VIEW [ IF EXISTS ] name
    SET SCHEMA new_schema
ALTER MATERIALIZED VIEW ALL IN TABLESPACE name [ OWNED BY role_name [, ... ] ]
    SET TABLESPACE new_tablespace [ NOWAIT ]

where action is one of:

    ALTER [ COLUMN ] column_name SET STATISTICS integer
    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 | DEFAULT }
    ALTER [ COLUMN ] column_name SET COMPRESSION compression_method
    CLUSTER ON index_name
    SET WITHOUT CLUSTER
    SET ACCESS METHOD new_access_method
    SET TABLESPACE new_tablespace
    SET ( storage_parameter [= value] [, ... ] )
    RESET ( storage_parameter [, ... ] )
    OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }

🦋 DESCRIPTION 🦋

ALTER MATERIALIZED VIEW changes various auxiliary properties of an existing materialized view. it's giving “let me tweak the side settings, not rewrite the whole query,” iykyk 💅

bestie, 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. and to alter the owner, you must be able to SET ROLE to 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 statement subforms and actions available for ALTER MATERIALIZED VIEW are a subset of those available for ALTER TABLE, and have the same meaning when used for materialized views. see the descriptions for ALTER TABLE for details. fr fr, that's the lore drop 📚

🌸 PARAMETERS 🌸

  • name — the name of an existing materialized view, optionally schema-qualified. yes, you can be fancy with the schema prefix 🎀
  • column_name — name of an existing column. specific column energy 💅
  • extension_name — the name of the extension that the materialized view is to depend on (or no longer dependent on, if NO is specified). a materialized view that's marked as dependent on an extension is automatically dropped when the extension is dropped. iconic dependency behavior, tbh 🦋
  • new_column_name — new name for an existing column. rename slay ✨
  • new_owner — the user name of the new owner of the materialized view. handover era 👑
  • new_name — the new name for the materialized view. glow-up name 🎀
  • new_schema — the new schema for the materialized view. moving houses, lowkey 🏠

🍓 EXAMPLES 🍓

to rename the materialized view foo to bar, you literally do this:

ALTER MATERIALIZED VIEW foo RENAME TO bar;

ate. no notes. 💅✨

🌈 COMPATIBILITY 🌈

ALTER MATERIALIZED VIEW is a PostgreSQL extension. periodt. 💖

⭐ SEE ALSO ⭐

💖 source/version: PostgreSQL 17.11 · date: 2026 · manual page: ALTER MATERIALIZED VIEW(7) — bye bestie, go alter something iconic! 🎀💅

📦 where this page comes from