pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Minghann Ho <Minghann.Ho@mcs.vuw.ac.nz>
Cc: pgsql-performance@postgresql.org
Subject: Re: alter table TBL add constraint TBL_FK foreign key ...
Date: Tue, 31 Dec 2002 19:38:54 -0800 (PST)
Message-ID: <20021231193351.U68640-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <200301011632.10433.Minghann.Ho@mcs.vuw.ac.nz>

On Wed, 1 Jan 2003, Minghann Ho wrote:

> I've experienced very slow performance to add foreign key constraints using
> ALTER TABLE ADD CONSTRAINT FOREIGN KEY ...
>
> After using COPY ... FROM to load the base tables, I started to build the
> referential integrity between tables.
> I have 3 tables: T1 (6 million records), T2 (1.5 million records) and T3 (0.8
> million records).
> One of the RI - foreign key (T1 -> T2) constraint took about 70 hrs to build.
> The other RI - foreign key (T1 -> T3) constraint took about 200 hrs and yet
> completed!! (compound foreign key)
>
> I tried to use small subset of the tables of T2 and T3 to do the testing.
> An estimation show that it need about 960 hrs to build the RI - foreign key
> constraints on table T1 -> T3 !!!

It's running the constraint check for each row in the foreign key table.
Rather than using a call to the function and a select for each row, it
could probably be done in a single select with a not exists subselect, but
that hasn't been done yet.  There's also been talk about allowing some
mechanism to allow the avoidance of the create time check, but I don't
think any concensus was reached.




view thread (4+ messages)  latest in thread

Message-ID: <20021231193351.U68640-100000@megazone23.bigpanda.com>
Permalink:  ../20021231193351.U68640-100000@megazone23.bigpanda.com/
Also on:    postgresql.org/message-id/20021231193351.U68640-100000@megazone23.bigpanda.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: sszabo@megazone23.bigpanda.com, Minghann.Ho@mcs.vuw.ac.nz
  Subject: Re: alter table TBL add constraint TBL_FK foreign key ...
  In-Reply-To: <20021231193351.U68640-100000@megazone23.bigpanda.com>
  References: <200301011632.10433.Minghann.Ho@mcs.vuw.ac.nz> <20021231193351.U68640-100000@megazone23.bigpanda.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox