← Back to branch summary

~ubuntu-branches/ubuntu/trusty/postgresql-8.4/trusty

« back to all changes in this revision

Viewing changes to doc/src/sgml/trigger.sgml

  • Committer: Bazaar Package Importer
  • Author(s): Martin Pitt
  • Date: 2009-07-11 16:59:35 UTC
  • mfrom: (5.1.1 karmic)
  • Revision ID: james.westby@ubuntu.com-20090711165935-jfwin6gfrxf0gfsi
Tags: 8.4.0-2
http://bugs.debian.org/536139
* debian/libpq-dev.install: Ship catalog/genbki.h. (Closes: #536139)
* debian/rules: Drop --enable-cassert for final release.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/src/sgml/trigger.sgml
1
 
<!-- $PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.55 2009/04/07 04:02:41 momjian Exp $ -->
 
1
<!-- $PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.56 2009/05/27 01:18:06 tgl Exp $ -->
2
2
 
3
3
 <chapter id="triggers">
4
4
  <title>Triggers</title>
250
250
   </para>
251
251
 
252
252
   <para>
 
253
    If your trigger function is written in any of the standard procedural
 
254
    languages, then the above statements apply only if the function is
 
255
    declared <literal>VOLATILE</>.  Functions that are declared
 
256
    <literal>STABLE</> or <literal>IMMUTABLE</> will not see changes made by
 
257
    the calling command in any case.
 
258
   </para>
 
259
 
 
260
   <para>
253
261
    Further information about data visibility rules can be found in
254
262
    <xref linkend="spi-visibility">.  The example in <xref
255
263
    linkend="trigger-example"> contains a demonstration of these rules.