Re: Integrity on large sites

From: Lew <lew(at)nospam(dot)lewscanon(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Integrity on large sites
Date: 2007-05-23 15:54:04
Message-ID: MaadncZYXekB_snbnZ2dnUVZ_jmdnZ2d@comcast.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

PFC wrote:
>>>> "*Really* big sites don't ever have referential
>>>> integrity. Or if the few spots they do (like with
>>>> financial transactions) it's implemented on the
>>> application level (via, say, optimistic locking), never the
>>> database level."
>
> Sure, but in the forum benchmark I just did, when using MyISAM, with
> no reference integrity checks, at the end of the benchmark, there is an
> impressive number of records with broken foreign key relations... when
> the user kills his HTTP connection or reloads at the wrong moment, and
> the script is interrupted, or killed by an exception or whatever, boom.

One assumes you mean implicit foreign key relations, since MyISAM doesn't
enforce them (hence the reason they're "broken", potentiated by the lack of
transaction support).

Sadly, there is a market for wrong answers faster.

--
Lew

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2007-05-23 15:56:28 Re: Tsearch2: upgrading from postgres 8.1.x to 8.2.x
Previous Message Joshua D. Drake 2007-05-23 15:51:16 Re: Tsearch2: upgrading from postgres 8.1.x to 8.2.x