ALTER_VIEW(7pg16)

✨ ALTER VIEW — bestie's guide to glow-ups for your views ✨

okay so this is the ALTER VIEW page from the PostgreSQL 16.15 documentation, and it's literally the manual for changing the definition of a view 💅 no cap, it's short, it's sweet, and it's gonna slay.

---

🌸 SYNOPSIS 🌸

like, here's the whole vibe in one look:

ALTER VIEW [ IF EXISTS ] name ALTER [ COLUMN ] column_name SET DEFAULT expression
ALTER VIEW [ IF EXISTS ] name ALTER [ COLUMN ] column_name DROP DEFAULT
ALTER VIEW [ IF EXISTS ] name OWNER TO { new_owner | CURRENT_ROLE | CURRENT_USER | SESSION_USER }
ALTER VIEW [ IF EXISTS ] name RENAME [ COLUMN ] column_name TO new_column_name
ALTER VIEW [ IF EXISTS ] name RENAME TO new_name
ALTER VIEW [ IF EXISTS ] name SET SCHEMA new_schema
ALTER VIEW [ IF EXISTS ] name SET ( view_option_name [= view_option_value] [, ... ] )
ALTER VIEW [ IF EXISTS ] name RESET ( view_option_name [, ... ] )

---

🦋 DESCRIPTION 🦋

ALTER VIEW changes various auxiliary properties of a view. that's the whole job 🫶

ok but real talk: if what you actually wanna do is modify the view's defining query, you do NOT use this — use CREATE OR REPLACE VIEW instead. different tool, different job, iykyk.

permissions check, and this is important so like, pay attention bestie 👑:

• you must own the view to use ALTER VIEW.
• to change a view's schema, you must also have CREATE privilege on the new schema.
• 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 view's schema.

and why are those restrictions there? bc they enforce that altering the owner doesn't do anything you couldn't already do by dropping and recreating the view. the math is mathing ✨

tiny exception, don't come for me: a superuser can alter ownership of any view anyway. main character energy fr.

---

💖 PARAMETERS 💖

• name — the name (optionally schema-qualified) of an existing view. yes, an existing one, we're not manifesting here.
• column_name — name of an existing column.
• new_column_name — new name for an existing column. she's rebranding 💅
• IF EXISTS — do not throw an error if the view does not exist. a notice is issued in this case. so chill, no drama, just a lil heads-up 🎀
• SET/DROP DEFAULT — these forms set or remove the default value for a column. and here's the tea: a view column's default value is substituted into any INSERT or UPDATE command whose target is the view, before applying any rules or triggers for the view. so the view's default will therefore take precedence over any default values from underlying relations. she wins, periodt 👑
• new_owner — the user name of the new owner of the view.
• new_name — the new name for the view.
• new_schema — the new schema for the view.
• SET ( view_option_name [= view_option_value] [, ... ] ) / RESET ( view_option_name [, ... ] ) — sets or resets a view option. currently supported options are, drumroll please 🥁:
  • check_option (enum) — changes the check option of the view. the value must be local or cascaded.
  • security_barrier (boolean) — changes the security-barrier property of the view. the value must be a Boolean value, such as true or false.
  • security_invoker (boolean) — changes the security-invoker property of the view. the value must be a Boolean value, such as true or false.

---

🌈 NOTES 🌈

for historical reasons, ALTER TABLE can be used with views too 🙈 but — and this is the catch — the only variants of ALTER TABLE that are allowed with views are equivalent to the ones shown above. so like, don't get creative, it's giving "same options, different font" 💀

---

🔥 EXAMPLES 🔥

to rename the view foo to bar:

ALTER VIEW foo RENAME TO bar;

to attach a default column value to an updatable view:

CREATE TABLE base_table (id int, ts timestamptz);
CREATE VIEW a_view AS SELECT * FROM base_table;
ALTER VIEW a_view ALTER COLUMN ts SET DEFAULT now();
INSERT INTO base_table(id) VALUES(1);  -- ts will receive a NULL
INSERT INTO a_view(id) VALUES(2);  -- ts will receive the current time

see how that works? the second insert goes through the view and gets now(), the first one goes straight to the table and gets NULL. the way that default takes precedence… obsessed 😭💜

---

⭐ COMPATIBILITY ⭐

ALTER VIEW is a PostgreSQL extension of the SQL standard. so bestie, this is our own special little thing, ngl 🌸

---

🧚 SEE ALSO 🧚

• CREATE VIEW (CREATE_VIEW(7))
• DROP VIEW (DROP_VIEW(7))

---

and that's the whole page, bestie 💖 this was PostgreSQL 16.15, dated 2026 — go forth and alter those views, you're gonna eat, no cap 🫶✨🎀