8000 Add more limited large object trigger example. · postgrespro/postgres_cluster@864de65 · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 864de65

Browse files
committed
Add more limited large object trigger example.
1 parent 9e84ccc commit 864de65

File tree

1 file changed

+2
-7
l 8000 ines changed

1 file changed

+2
-7
lines changed

doc/src/sgml/lo.sgml

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -77,13 +77,8 @@ CREATE TRIGGER t_raster BEFORE UPDATE OR DELETE ON image
7777
For each column that will contain unique references to large objects,
7878
create a <literal>BEFORE UPDATE OR DELETE</> trigger, and give the column
7979
name as the sole trigger argument. You can also restrict the trigger
80-
to only execute on updates to the column with:
81-
82-
<programlisting>
83-
CREATE TRIGGER t_raster BEFORE UPDATE OF raster OR DELETE ON image
84-
FOR EACH ROW EXECUTE PROCEDURE lo_manage(raster);
85-
</programlisting>
86-
80+
to only execute on updates to the column by using <literal>BEFORE UPDATE
81+
OF</literal> <replaceable class="parameter">column_name</replaceable>.
8782
If you need multiple <type>lo</>
8883
columns in the same table, create a separate trigger for each one,
8984
remembering to give a different name to each trigger on the same table.

0 commit comments

Comments
 (0)
0