database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-25 12:03:53 +03:00
Code Activity

Improve documentation about function volatility: mention the snapshot

Browse Source 
visibility effects in a couple of places where people are likely to look
for it.  Per discussion of recent question from Karl Nack.
This commit is contained in:
Tom Lane
2009-05-27 01:18:06 +00:00
parent 48938ab506
commit 253ff58a1d
2 changed files with 44 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/trigger.sgml
View File

@@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.55 2009/04/07 04:02:41 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.56 2009/05/27 01:18:06 tgl Exp $ -->
<chapter id="triggers">
<title>Triggers</title>
@@ -249,6 +249,14 @@
</itemizedlist>
</para>
<para>
If your trigger function is written in any of the standard procedural
languages, then the above statements apply only if the function is
declared <literal>VOLATILE</>. Functions that are declared
<literal>STABLE</> or <literal>IMMUTABLE</> will not see changes made by
the calling command in any case.
</para>
<para>
Further information about data visibility rules can be found in
<xref linkend="spi-visibility">. The example in <xref