From 864de654c8271ab7f9fb8397fcc665ffed93645c Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 14 Aug 2012 23:25:20 -0400
Subject: [PATCH] Add more limited large object trigger example.

---
 doc/src/sgml/lo.sgml | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/doc/src/sgml/lo.sgml b/doc/src/sgml/lo.sgml
index 0c11fdc20aa..cd4ed6030b7 100644
--- a/doc/src/sgml/lo.sgml
+++ b/doc/src/sgml/lo.sgml
@@ -77,13 +77,8 @@ CREATE TRIGGER t_raster BEFORE UPDATE OR DELETE ON image
    For each column that will contain unique references to large objects,
    create a <literal>BEFORE UPDATE OR DELETE</> trigger, and give the column
    name as the sole trigger argument.  You can also restrict the trigger
-   to only execute on updates to the column with:
-
-<programlisting>
-CREATE TRIGGER t_raster BEFORE UPDATE OF raster OR DELETE ON image
-    FOR EACH ROW EXECUTE PROCEDURE lo_manage(raster);
-</programlisting>
-
+   to only execute on updates to the column by using <literal>BEFORE UPDATE
+   OF</literal> <replaceable class="parameter">column_name</replaceable>.
    If you need multiple <type>lo</>
    columns in the same table, create a separate trigger for each one,
    remembering to give a different name to each trigger on the same table.