diff --git a/doc/src/sgml/event-trigger.sgml b/doc/src/sgml/event-trigger.sgml
index c10627554bd..1197de78d02 100644
--- a/doc/src/sgml/event-trigger.sgml
+++ b/doc/src/sgml/event-trigger.sgml
@@ -147,13 +147,15 @@
     <title>table_rewrite</title>
 
    <para>
-    The <literal>table_rewrite</literal> event occurs just before a table is
-    rewritten by some actions of the commands <literal>ALTER TABLE</literal> and
-    <literal>ALTER TYPE</literal>.  While other
-    control statements are available to rewrite a table,
+    The <literal>table_rewrite</literal> event occurs just before a table or
+    materialized view is rewritten by some actions of the commands
+    <literal>ALTER TABLE</literal> and <literal>ALTER MATERIALIZED VIEW</literal>.
+    It can also be triggered by <literal>ALTER TYPE</literal> when a change to
+    a composite type causes one of its typed tables to be rewritten.
+    While other control statements are available to rewrite a relation,
     like <literal>CLUSTER</literal> and <literal>VACUUM</literal>,
     the <literal>table_rewrite</literal> event is not triggered by them.
-    To find the OID of the table that was rewritten, use the function
+    To find the OID of the relation being rewritten, use the function
     <literal>pg_event_trigger_table_rewrite_oid()</literal>, to discover the
     reason(s) for the rewrite, use the function
     <literal>pg_event_trigger_table_rewrite_reason()</literal> (see <xref
diff --git a/src/test/regress/expected/event_trigger.out b/src/test/regress/expected/event_trigger.out
index f57e8ffa7a5..d3e1009715b 100644
--- a/src/test/regress/expected/event_trigger.out
+++ b/src/test/regress/expected/event_trigger.out
@@ -587,11 +587,11 @@ alter table rewriteme alter column foo type numeric;
 ERROR:  rewrites not allowed
 CONTEXT:  PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE
 alter table rewriteme add column baz int default 0;
--- test with more than one reason to rewrite a single table
+-- test with more than one reason to rewrite a single table or matview
 CREATE OR REPLACE FUNCTION test_evtrig_no_rewrite() RETURNS event_trigger
 LANGUAGE plpgsql AS $$
 BEGIN
-  RAISE NOTICE 'Table ''%'' is being rewritten (reason = %)',
+  RAISE NOTICE 'Relation ''%'' is being rewritten (reason = %)',
                pg_event_trigger_table_rewrite_oid()::regclass,
                pg_event_trigger_table_rewrite_reason();
 END;
@@ -600,11 +600,11 @@ alter table rewriteme
  add column onemore int default 0,
  add column another int default -1,
  alter column foo type numeric(10,4);
-NOTICE:  Table 'rewriteme' is being rewritten (reason = 4)
+NOTICE:  Relation 'rewriteme' is being rewritten (reason = 4)
 -- matview rewrite when changing access method
 CREATE MATERIALIZED VIEW heapmv USING heap AS SELECT 1 AS a;
 ALTER MATERIALIZED VIEW heapmv SET ACCESS METHOD heap2;
-NOTICE:  Table 'heapmv' is being rewritten (reason = 8)
+NOTICE:  Relation 'heapmv' is being rewritten (reason = 8)
 DROP MATERIALIZED VIEW heapmv;
 -- shouldn't trigger a table_rewrite event
 alter table rewriteme alter column foo type numeric(12,4);
@@ -615,7 +615,7 @@ set timezone to '0';
 alter table rewriteme alter column bar type timestamptz;
 set timezone to 'Europe/London';
 alter table rewriteme alter column bar type timestamp; -- does rewrite
-NOTICE:  Table 'rewriteme' is being rewritten (reason = 4)
+NOTICE:  Relation 'rewriteme' is being rewritten (reason = 4)
 rollback;
 -- typed tables are rewritten when their type changes.  Don't emit table
 -- name, because firing order is not stable.
diff --git a/src/test/regress/sql/event_trigger.sql b/src/test/regress/sql/event_trigger.sql
index 32e9bb58c5e..cb1b5a1aa04 100644
--- a/src/test/regress/sql/event_trigger.sql
+++ b/src/test/regress/sql/event_trigger.sql
@@ -422,11 +422,11 @@ insert into rewriteme
 alter table rewriteme alter column foo type numeric;
 alter table rewriteme add column baz int default 0;
 
--- test with more than one reason to rewrite a single table
+-- test with more than one reason to rewrite a single table or matview
 CREATE OR REPLACE FUNCTION test_evtrig_no_rewrite() RETURNS event_trigger
 LANGUAGE plpgsql AS $$
 BEGIN
-  RAISE NOTICE 'Table ''%'' is being rewritten (reason = %)',
+  RAISE NOTICE 'Relation ''%'' is being rewritten (reason = %)',
                pg_event_trigger_table_rewrite_oid()::regclass,
                pg_event_trigger_table_rewrite_reason();
 END;