diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml
index 920981e..d868889 100644
--- a/doc/src/sgml/plperl.sgml
+++ b/doc/src/sgml/plperl.sgml
@@ -1229,7 +1229,7 @@ CREATE TRIGGER test_valid_id_trig
Event trigger procedures can be written in PL/Perl.
- PostgreSQL requires that a procedure that is to be called
+ PostgreSQL requires that a procedure to be called
as a trigger must be declared as a function with no arguments
and a return type of command_trigger.
@@ -1272,7 +1272,7 @@ CREATE TRIGGER test_valid_id_trig
$_TD->{objectname}
- The name of the objectthat caused the trigger procedure
+ The name of the object that caused the trigger procedure
to be invoked.
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index b71786e..102dfff 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -3940,7 +3940,7 @@ SELECT * FROM sales_summary_bytime;
- When a PL/pgSQL function is called as a
+ When a PL/pgSQL function is called as an
event trigger, several special variables are created automatically
in the top-level block. They are:
@@ -3981,7 +3981,7 @@ SELECT * FROM sales_summary_bytime;
Data type name; the name of the schema of the object
- that caused the trigger invocation. Can be NULL
+ that caused the trigger invocation. This is NULL
for objects not located in a schema.
@@ -4004,7 +4004,7 @@ SELECT * FROM sales_summary_bytime;
- shows an example of a
+ shows an example of an
event trigger procedure in PL/pgSQL.
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index 07f017a..d62da16 100644
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -881,7 +881,7 @@ $$ LANGUAGE plpythonu;
Event trigger procedures can be written in PL/Python.
- PostgreSQL requires that a procedure that is to be called
+ PostgreSQL requires that a procedure to be called
as a trigger must be declared as a function with no arguments
and a return type of event_trigger.
@@ -924,7 +924,7 @@ $$ LANGUAGE plpythonu;
TD["objectname"]
- The name of the objectthat caused the trigger procedure
+ The name of the object that caused the trigger procedure
to be invoked.
diff --git a/doc/src/sgml/pltcl.sgml b/doc/src/sgml/pltcl.sgml
index c9a4e4c..1975976 100644
--- a/doc/src/sgml/pltcl.sgml
+++ b/doc/src/sgml/pltcl.sgml
@@ -527,7 +527,7 @@ SELECT 'doesn''t' AS ret
Trigger procedures can be written in PL/Tcl.
- PostgreSQL requires that a procedure that is to be called
+ PostgreSQL requires that a procedure to be called
as a trigger must be declared as a function with no arguments
and a return type of trigger.
@@ -725,8 +725,8 @@ CREATE TRIGGER trig_mytab_modcount BEFORE INSERT OR UPDATE ON mytab
Event trigger procedures can be written in PL/Tcl.
- PostgreSQL requires that a procedure that is to be called
- as a trigger must be declared as a function with no arguments
+ PostgreSQL requires that a procedure to be called
+ as an event trigger must be declared as a function with no arguments
and a return type of event_trigger.
@@ -768,7 +768,7 @@ CREATE TRIGGER trig_mytab_modcount BEFORE INSERT OR UPDATE ON mytab
$TG_objectname
- The name of the objectthat caused the trigger procedure
+ The name of the object that caused the trigger procedure
to be invoked.
diff --git a/doc/src/sgml/ref/alter_event_trigger.sgml b/doc/src/sgml/ref/alter_event_trigger.sgml
index b21ce75..74882e4 100644
--- a/doc/src/sgml/ref/alter_event_trigger.sgml
+++ b/doc/src/sgml/ref/alter_event_trigger.sgml
@@ -12,7 +12,7 @@ PostgreSQL documentation
ALTER EVENT TRIGGER
- change the definition of a trigger
+ change the definition of an event trigger
@@ -31,8 +31,6 @@ ALTER EVENT TRIGGER name RENAME TO
ENABLE REPLICA
DISABLE
-and where command can be one of the same list as in .
-
@@ -45,7 +43,7 @@ ALTER EVENT TRIGGER name RENAME TO
- You must be superuser to alter a event trigger.
+ You must be superuser to alter an event trigger.
diff --git a/doc/src/sgml/ref/create_event_trigger.sgml b/doc/src/sgml/ref/create_event_trigger.sgml
index af06c88..bd323b7 100644
--- a/doc/src/sgml/ref/create_event_trigger.sgml
+++ b/doc/src/sgml/ref/create_event_trigger.sgml
@@ -12,7 +12,7 @@ PostgreSQL documentation
CREATE EVENT TRIGGER
- define a new trigger
+ define a new event trigger
@@ -135,7 +135,7 @@ CREATE EVENT TRIGGER name
The command trigger gives a procedure to fire before the event is
executed. In some cases the procedure can be fired instead of the event
code PostgreSQL would run itself. A command trigger's function must
- return event_trigger data type. It can then only
+ return a data type of event_trigger. It can then only
abort the execution of the command by raising an exception.
@@ -146,8 +146,8 @@ CREATE EVENT TRIGGER name
Note that objects dropped by the effect of DROP
- CASCADE will not result in a event trigger firing, only the
- top-level event for the main object will fire a event trigger. That
+ CASCADE will not result in an event trigger firing, only the
+ top-level event for the main object will fire an event trigger. That
also applies to other dependencies following, as in DROP OWNED
BY.
@@ -178,7 +178,8 @@ CREATE EVENT TRIGGER name
The tag of the command the trigger is for. Supported commands are
mainly those acting on database objects, plus some more facilities.
- That leaves out the following list of non supported commands.
+ That leaves the following cases where commands are not supported by
+ event trigger functionality.
Commands that refer to global objects, such as databases, tablespaces
@@ -209,7 +210,7 @@ CREATE EVENT TRIGGER name
Triggers on ANY command support more commands than
just this list, and will only provide the command
tag argument as NOT NULL. Supporting more
- commands is made so that you can actually block
+ commands is made so that you can block all
commands in one go.
@@ -220,7 +221,7 @@ CREATE EVENT TRIGGER name
A user-supplied function that is declared as taking no argument and
- returning type event trigger.
+ returning type event_trigger.
If your event trigger is implemented in C then it
@@ -238,11 +239,11 @@ CREATE EVENT TRIGGER name
Notes
- To create a trigger on a event, the user must be superuser.
+ To create a trigger on an event, the user must be a superuser.
- Use to remove a event trigger.
+ Use to remove an event trigger.
diff --git a/doc/src/sgml/ref/drop_event_trigger.sgml b/doc/src/sgml/ref/drop_event_trigger.sgml
index fc45dff..006f136 100644
--- a/doc/src/sgml/ref/drop_event_trigger.sgml
+++ b/doc/src/sgml/ref/drop_event_trigger.sgml
@@ -12,7 +12,7 @@ PostgreSQL documentation
DROP EVENT TRIGGER
- remove a event trigger
+ remove an event trigger
@@ -30,7 +30,7 @@ DROP EVENT TRIGGER [ IF EXISTS ] name
DROP EVENT TRIGGER removes an existing trigger definition.
- To execute this command, the current user must be superuser.
+ To execute this command, the current user must be a superuser.
diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index 32994b9..dd18e7b 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -39,8 +39,8 @@
A trigger is a specification that the database should automatically
execute a particular function whenever a certain command is performed.
- The whole set of PostgreSQL commands is not
- supported for triggers, see
+ Not all PostgreSQL commands are supported
+ for triggers. See
for details.