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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: FOREIGN KEYS vs PERFORMANCE


  • From: "Jim C. Nasby" <jnasby(at)pervasive(dot)com>
  • To: Michael Glaesemann <grzm(at)myrealbox(dot)com>
  • Cc: Rodrigo Sakai <rodrigo(dot)sakai(at)zanthus(dot)com(dot)br>, pgsql-performance(at)postgresql(dot)org
  • Subject: Re: FOREIGN KEYS vs PERFORMANCE
  • Date: Tue, 11 Apr 2006 18:38:20 -0500
  • Message-id: <20060411233820(dot)GB49405(at)pervasive(dot)com>

On Wed, Apr 12, 2006 at 08:06:17AM +0900, Michael Glaesemann wrote:
> 
> On Apr 12, 2006, at 4:13 , Rodrigo Sakai wrote:
> 
> >  I think this is an old question, but I want to know if it really  
> >is well worth to not create some foreign keys an deal with the  
> >referential integrity at application-level?????
> 
> If I had to choose between one or the other, I'd leave all  
> referential integrity in the database and deal with the errors thrown  
> when referential integrity is violated in the application. PostgreSQL  
> is designed to handle these kinds of issues. Anything you code in  
> your application is more likely to contain bugs or miss corner cases  
> that would allow referential integrity to be violated. PostgreSQL has  
> been pounded on for years by a great many users and developers,  
> making the likelihood of bugs still remaining much smaller.

It's also pretty unlikely that you can make RI in the application
perform better than in the database.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group