Documentation fix: s/event_object_name/event_object_table/g

diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index 400d0e871d2ea3c8d8f387ae1d4de116f628c537..c451e332e8fd6e63cc97927b604e15463cdeab06 100644 (file)
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -3822,7 +3822,7 @@ ORDER BY c.ordinal_position;
      </row>
 
      <row>
-      <entry><literal>event_object_name</literal></entry>
+      <entry><literal>event_object_table</literal></entry>
       <entry><type>sql_identifier</type></entry>
       <entry>Name of the table that the trigger is defined on</entry>
      </row>
@@ -3901,7 +3901,7 @@ ORDER BY c.ordinal_position;
    event.  As a consequence of these two issues, the primary key of
    the view <literal>triggers</literal> is really
    <literal>(trigger_catalog, trigger_schema, trigger_name,
-   event_object_name, event_manipulation)</literal> instead of
+   event_object_table, event_manipulation)</literal> instead of
    <literal>(trigger_catalog, trigger_schema, trigger_name)</literal>,
    which is what the SQL standard specifies.  Nonetheless, if you
    define your triggers in a manner that conforms with the SQL