From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
Cc: | Pgsql-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: on update / on delete performance of foreign keys |
Date: | 2005-01-24 13:50:12 |
Message-ID: | 41F4FD14.1040401@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Florian G. Pflug wrote:
> Hi
>
> I ran into some performance problems regarding foreign keys lately.
> My schema has about 20 tables, which each contain from 10 to 100.000
> records. They have quite complicated interdependencies, modeled using
> foregin keys set to "on update cascade, on delete cascade".
> The schema stores data for multiple customers - Recently I wanted
> to extract the data for just a single customer. I duplicated the schema,
> and deleted all but one customer from the "customer" table. This worked
> as expected, but the delete took a few hours (!) on a moderatly fast
> machine (dual 1GHz PIII, RAID5-Array for postgres-data).
PostgreSQL doesn't automatically add indexes to foreign-key columns.
That sounds like the issue to me.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2005-01-24 14:24:49 | Re: How are foreign key constraints built? |
Previous Message | Florian G. Pflug | 2005-01-24 12:10:34 | on update / on delete performance of foreign keys |