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/
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
