CREATE_MATERIALIZED_VIEW(7pg14)

💅 CREATE MATERIALIZED VIEW 💅

okay bestie, you found the CREATE_MATERIALIZED_VIEW(7pg14) page from the PostgreSQL 14.24 Documentation — and it's literally the manual page for defining a new materialized view. grab a strawberry 🍓, we're doing this.

🌸 NAME 🌸

CREATE_MATERIALIZED_VIEW — define a new materialized view. periodt. 💖

✨ SYNOPSIS ✨

CREATE MATERIALIZED VIEW [ IF NOT EXISTS ] table_name
    [ (column_name [, ...] ) ]
    [ USING method ]
    [ WITH ( storage_parameter [= value] [, ... ] ) ]
    [ TABLESPACE tablespace_name ]
    AS query
    [ WITH [ NO ] DATA ]

💖 DESCRIPTION 💖

CREATE MATERIALIZED VIEW defines a materialized view of a query. The query is executed and used to populate the view at the time the command is issued (unless WITH NO DATA is used) and may be refreshed later using REFRESH MATERIALIZED VIEW.

It's similar to CREATE TABLE AS, except that it also remembers the query used to initialize the view, so that it can be refreshed later upon demand — the way it remembers is iconic. A materialized view has many of the same properties as a table, but there is no support for temporary materialized views. not me checking for temp support... there is none.

CREATE MATERIALIZED VIEW requires CREATE privilege on the schema used for the materialized view. so yes, permissions check first, bestie 🔑

🎀 PARAMETERS 🎀

• IF NOT EXISTS — do not throw an error if a materialized view with the same name already exists. A notice is issued in this case. Note that there is no guarantee that the existing materialized view is anything like the one that would have been created. iykyk, "if not exists" is not a promise that the existing thing is your vibe.
• table_name — the name (optionally schema-qualified) of the materialized view to be created. name it, bestie.
• column_name — the name of a column in the new materialized view. If column names are not provided, they are taken from the output column names of the query.
• USING method — this optional clause specifies the table access method to use to store the contents for the new materialized view; the method needs be an access method of type TABLE. See Chapter 61 for more information. If this option is not specified, the default table access method is chosen for the new materialized view. See default_table_access_method for more information.
• WITH ( storage_parameter [= value] [, ... ] ) — this clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE (CREATE_TABLE(7)) documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW. See CREATE TABLE (CREATE_TABLE(7)) for more information.
• TABLESPACE tablespace_name — the tablespace_name is the name of the tablespace in which the new materialized view is to be created. If not specified, default_tablespace is consulted.
• query — a SELECT, TABLE, or VALUES command. This query will run within a security-restricted operation; in particular, calls to functions that themselves create temporary tables will fail. heads up: this is a real caveat, not a drill.
• WITH [ NO ] DATA — this clause specifies whether or not the materialized view should be populated at creation time. If not, the materialized view will be flagged as unscannable and cannot be queried until REFRESH MATERIALIZED VIEW is used. so if you skip the data, it's lowkey unqueryable until you refresh. facts.

🦋 COMPATIBILITY 🦋

CREATE MATERIALIZED VIEW is a PostgreSQL extension. slay, it's ours 💅

🌈 SEE ALSO 🌈

• ALTER MATERIALIZED VIEW (ALTER_MATERIALIZED_VIEW(7))
• CREATE TABLE AS (CREATE_TABLE_AS(7))
• CREATE VIEW (CREATE_VIEW(7))
• DROP MATERIALIZED VIEW (DROP_MATERIALIZED_VIEW(7))
• REFRESH MATERIALIZED VIEW (REFRESH_MATERIALIZED_VIEW(7))

okay that's the whole page, bestie — from the PostgreSQL 14.24 Documentation, dated 2026. now go define that materialized view and serve looks ✨💖👑