| From: | Demian Lessa <demian(at)lessa(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Constraint enforcement |
| Date: | 2007-02-15 16:15:20 |
| Message-ID: | 45D48718.4040406@lessa.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Is there any documentation other than the soruce code on how postgres
performs the appropriate (PK, FK, CHECK, UNIQUE) constraint enforcement
on DELETEs, UPDATEs, and INSERTs?
What I'm trying to figure out is how postgre identifies the *exact* set
of constraints to enforce for each of the different commands above, and
the order in which these are performed (since some checks are way more
expensive than others).
Thank you,
Demian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFF1IcYWs7G5iIp9akRAgM4AKChLgEMZRJC36hpEPDtPBPjrVfFJwCfSe43
B1KNLqOsn5qQnbXPnup2n7A=
=kABQ
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Jones | 2007-02-15 16:18:39 | Re: Recover anything from dropped database? |
| Previous Message | Tom Lane | 2007-02-15 15:57:39 | Re: WARNING: some databases have not been vacuumed in 1953945422 transactions |