Message-ID: <45044013.8020003@commandprompt.com>
Date: Sun, 10 Sep 2006 09:40:51 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Thunderbird 1.5.0.5 (X11/20060728)
MIME-Version: 1.0
To: Gregory Stark <gsstark@mit.edu>
CC: Tom Lane <tgl@sss.pgh.pa.us>,
 Stephan Szabo <sszabo@megazone.bigpanda.com>,
	Chris Mair <chrisnospam@1006.org>,
	MAR - Secretariado Geral <secretariadogeral@acra.pt>,
	pgsql-hackers@postgresql.org
Subject: Re: Foreign keys
References: <000601c6d463$208cb160$0500a8c0@SECGERAL>
	<1157877370.26364.11.camel@ultra.home.lan>	<87venw6qw3.fsf@enterprisedb.com>
	<20060910070805.T99308@megazone.bigpanda.com>	<6967.1157900971@sss.pgh.pa.us>
	<87ac57vggk.fsf@stark.xeocode.com>
In-Reply-To: <87ac57vggk.fsf@stark.xeocode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


> In any case the same logic that leads to it being desirable to report all the
> errors to the user in a UI and not just report them one by one also applies to
> the database. I'm not sure it's the most important issue in the world, but it
> does seem like a "it would be nice" feature if it reported all the errors in
> the statement, not just the first one it finds.
> 

Seems kind of extraneous to me. I am guessing it would cause yet further 
overhead with our foreign key checks.

My testing shows that the use of foreign keys on high velocity single 
transaction loads, can cause easily a 50% reduction in performance. Why 
add to that? What we need to be doing is finding a way to decrease the 
impact of foreign key checks.

Sincerely,

Joshua D. Drake

-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/