Re: FOREIGN KEYS vs PERFORMANCE

From: Michael Glaesemann <grzm(at)myrealbox(dot)com>
To: "Rodrigo Sakai" <rodrigo(dot)sakai(at)zanthus(dot)com(dot)br>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: FOREIGN KEYS vs PERFORMANCE
Date: 2006-04-11 23:06:17
Message-ID: 72C39159-1A4B-4595-A978-1DF57AD42527@myrealbox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


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.

Of course, you can add some referential integrity checks in your
application code, but those should be in addition to your database-
level checks.

Michael Glaesemann
grzm myrealbox com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2006-04-11 23:38:20 Re: FOREIGN KEYS vs PERFORMANCE
Previous Message Jim C. Nasby 2006-04-11 22:59:14 Re: freebsd/softupdates for data dir