diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 561f6e50d63..6f77c0715e6 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -4307,11 +4307,6 @@ ASSERT condition ,
-
- shows an example of a
- trigger function in PL/pgSQL.
-
-
A PL/pgSQL Trigger Function
@@ -4361,8 +4356,6 @@ CREATE TRIGGER emp_stamp BEFORE INSERT OR UPDATE ON emp
Another way to log changes to a table involves creating a new table that
holds a row for each insert, update, or delete that occurs. This approach
can be thought of as auditing changes to a table.
- shows an example of an
- audit trigger function in PL/pgSQL.
@@ -4418,8 +4411,6 @@ AFTER INSERT OR UPDATE OR DELETE ON emp
approach still records the full audit trail of changes to the table,
but also presents a simplified view of the audit trail, showing just
the last modified timestamp derived from the audit trail for each entry.
- shows an example
- of an audit trigger on a view in PL/pgSQL.
@@ -4498,9 +4489,6 @@ INSTEAD OF INSERT OR UPDATE OR DELETE ON emp_view
times.
This technique is commonly used in Data Warehousing, where the tables
of measured or observed data (called fact tables) might be extremely large.
- shows an example of a
- trigger function in PL/pgSQL that maintains
- a summary table for a fact table in a data warehouse.
@@ -4652,7 +4640,6 @@ SELECT * FROM sales_summary_bytime;
statement. The CREATE TRIGGER command assigns names to one
or both transition tables, and then the function can refer to those names
as though they were read-only temporary tables.
- shows an example.
@@ -4760,12 +4747,7 @@ CREATE TRIGGER emp_audit_del
-
- shows an example of an
- event trigger function in PL/pgSQL.
-
-
-
+
A PL/pgSQL Event Trigger Function