[LucaCappelletti94]

ALTER MATERIALIZED VIEW did not parse. After ALTER the parser expected an object keyword and stopped at MATERIALIZED, so a PostgreSQL schema that hands a materialized view to its owner, renames it or sets a storage parameter on it could not be read.

The statement reuses the AlterView node from #2730 with a materialized flag, since the two share their operations. OWNER TO, RENAME TO, RENAME COLUMN, SET SCHEMA, SET (...) and RESET (...) parse and round-trip through Display, and AS and ALTER COLUMN stay refused after MATERIALIZED.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.84%. Comparing base (45fe354) to head (f6447ab).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2776   +/-   ##
=======================================
  Coverage   82.83%   82.84%           
=======================================
  Files          42       42           
  Lines       35900    35907    +7     
  Branches    35900    35907    +7     
=======================================
+ Hits        29739    29746    +7     
  Misses       2654     2654           
  Partials     3507     3507           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sabir-akhadov-localstack]

PG 16 does accept ALTER MATERIALIZED VIEW m ALTER COLUMN c SET STATISTICS 100 / SET (n_distinct = 10) / SET STORAGE PLAIN; only SET/DROP DEFAULT is refused. This branch will have to be undone once AlterColumn grows those variants, so it may be simpler to drop it now and let AS/default-related forms fall through as they do for plain views.