Skip site navigation (1) Skip section navigation (2)

pgsql: Disallow referential integrity actions from being deferred; only

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Disallow referential integrity actions from being deferred; only
Date: 2004-10-21 21:34:00
Message-ID: 20041021213400.7343E32A272@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Disallow referential integrity actions from being deferred; only the
NO ACTION check is deferrable.  This seems to be a closer approximation
to what the SQL spec says than what we were doing before, and it prevents
some anomalous behaviors that are possible now that triggers can fire
during the execution of PL functions.
Stephan Szabo.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        ddl.sgml (r1.30 -> r1.31)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ddl.sgml.diff?r1=1.30&r2=1.31)
    pgsql/doc/src/sgml/ref:
        create_table.sgml (r1.84 -> r1.85)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_table.sgml.diff?r1=1.84&r2=1.85)
    pgsql/src/backend/commands:
        tablecmds.c (r1.135 -> r1.136)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablecmds.c.diff?r1=1.135&r2=1.136)
        trigger.c (r1.172 -> r1.173)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/trigger.c.diff?r1=1.172&r2=1.173)

pgsql-committers by date

Next:From: Tom LaneDate: 2004-10-21 22:48:55
Subject: pgsql: Update obsolete comments about COPY vs INSERT options, per Uwe
Previous:From: Tom LaneDate: 2004-10-21 20:23:19
Subject: pgsql: Set the close-on-exec flag for libpq's socket to the backend, to

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group