Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ade9505

Browse files
committed
Update set constraints man page
1 parent 0fe9b39 commit ade9505

File tree

1 file changed

+9
-10
lines changed

1 file changed

+9
-10
lines changed

doc/src/sgml/ref/set.sgml

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.40 2000/04/14 15:17:28 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.41 2000/04/14 23:12:29 momjian Exp $
33
Postgres documentation
44
-->
55

@@ -269,10 +269,9 @@ SELECT setseed(<replaceable>value</replaceable>);
269269
<term>CONSTRAINT</term>
270270
<listitem>
271271
<para>
272-
SET CONSTRAINTS is the SQL3 specified command to change the
273-
default behaviour of constraints with respect to deferring in the current
274-
transaction. Allowed parameters are:
275-
272+
SET CONSTRAINTS controls the frequency of foreign key
273+
constratint checking in the current transaction. Allowed
274+
parameters are:
276275
<variablelist>
277276
<varlistentry>
278277
<term><replaceable class="parameter">constraintlist</replaceable></term>
@@ -296,11 +295,11 @@ SELECT setseed(<replaceable>value</replaceable>);
296295
</para>
297296

298297
<para>
299-
In deferred mode, the actual check of the constraint is held
300-
back until either its mode is explicitly set to <option>IMMEDIATE</option>,
301-
or until COMMIT. This is actually only done for foreign key
302-
constraints, so it does not apply to UNIQUE or other
303-
constraints.
298+
In <option>DEFERRED</option> mode, foreign key constraints
299+
marked as <option>DEFERRABLE</option> are checked only at
300+
transaction commit.
301+
In <option>IMMEDIATE</option> mode, foreign key constraints
302+
are checked at the end of each query.
304303
</para>
305304
</listitem>
306305
</varlistentry>

0 commit comments

Comments
 (0)