aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2000-05-17 17:44:13 +0000
committerBruce Momjian <bruce@momjian.us>2000-05-17 17:44:13 +0000
commit21258c35a0777437c1ded2e4a2a72947fd71587b (patch)
tree09bc93836265a70d7ce4e6c29ca4ddace0f03a79
parent362a0f68d9278016ba5883095f2d4b5ace30618d (diff)
downloadpostgresql-21258c35a0777437c1ded2e4a2a72947fd71587b.tar.gz
postgresql-21258c35a0777437c1ded2e4a2a72947fd71587b.zip
Clean up trigger sgml docs.
-rw-r--r--doc/src/sgml/trigger.sgml15
1 files changed, 7 insertions, 8 deletions
diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index 1e76524baee..4d4882aacd1 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -2,13 +2,12 @@
<title>Triggers</title>
<para>
- <productname>Postgres</productname> has various client interfaces
- such as Perl, Tcl, Python and C, as well as three
- <firstterm>Procedural Languages</firstterm>
- (PL). It is also possible
- to call C functions as trigger actions. Note that STATEMENT-level trigger
- events are not supported in the current version. You can currently specify
- BEFORE or AFTER on INSERT, DELETE or UPDATE of a tuple as a trigger event.
+ <productname>Postgres</productname> has various server-side function
+ interfaces. Server-side functions can be written in SQL, PLPGSQL,
+ TCL, or C. Trigger functions can be written in any of these
+ languages. Note that STATEMENT-level trigger events are not supported
+ in the current version. You can currently specify BEFORE or AFTER on
+ INSERT, DELETE or UPDATE of a tuple as a trigger event.
</para>
<sect1>
@@ -98,7 +97,7 @@ CREATE TRIGGER <replaceable>trigger</replaceable> [ BEFORE | AFTER ] [ INSERT |
<term><replaceable>procedure</replaceable></term>
<listitem>
<para>
- The procedure name is the C function called.
+ The procedure name is the function called.
</para>
</listitem>
</varlistentry>