ALTER_MATERIALIZED_VIEW(7pg14)

🌸 NAME 🌸

okay bestie, this is the ALTER MATERIALIZED VIEW(7) page, aka ALTER_MATERIALIZED_VIEW — and its whole thing is changing the definition of a materialized view. no cap, that’s the name + job. 💅

---

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

---

🦋 DESCRIPTION 🦋

okay so ALTER MATERIALIZED VIEW changes various auxiliary properties of an existing materialized view. that’s the vibe. ✨

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.

💀 permissions tea: 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. slay for the superuser, i guess.

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. 🫶

---

🎀 PARAMETERS 🎀

• name — the name (optionally schema-qualified) of an existing materialized view. 💖
• column_name — name of an existing column. 📌
• 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. 💥
• new_column_name — new name for an existing column. 🎀
• new_owner — the user name of the new owner of the materialized view. 👑
• new_name — 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, you literally run:

ALTER MATERIALIZED VIEW foo RENAME TO bar;

---

💜 COMPATIBILITY 💜

ALTER MATERIALIZED VIEW is a PostgreSQL extension. periodt. ✨

---

🌟 SEE ALSO 🌟

• CREATE MATERIALIZED VIEW (CREATE_MATERIALIZED_VIEW(7))
• DROP MATERIALIZED VIEW (DROP_MATERIALIZED_VIEW(7))
• REFRESH MATERIALIZED VIEW (REFRESH_MATERIALIZED_VIEW(7))

---

💖 footer tea: PostgreSQL 14.24, dated 2026 — that’s the source/version + date vibe, bye bestie! 💖