From: Jim C. Nasby <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Enzo Daddario <enzo@pienetworks.com>
Cc: PGADMIN <pgsql-admin@postgresql.org>
Subject: Re: Constraint question
Date: Mon, 15 May 2006 10:12:49 -0500
Message-ID: <20060515151249.GE26212@pervasive.com> (raw)
In-Reply-To: <21805.1147661450@sss.pgh.pa.us>
References: <1147659556.29084.26.camel@localhost.localdomain>
<21805.1147661450@sss.pgh.pa.us>
On Sun, May 14, 2006 at 10:50:50PM -0400, Tom Lane wrote:
> Enzo Daddario <enzo@pienetworks.com> writes:
> > I am now required the remove thousands of obsolete records from table
> > "X" and even though I have removed all related rows in all related
> > tables, the deletion of rows in table "X" is taking WAY TOO LONG.
>
> You need to put indexes on the referencing columns. Then start a fresh
> session for doing the actual deletes (FK check plans are usually cached
> per-session).
Would SET CONSTRAINTS ... DEFERRED not help, or does it still use the
same machinery to do the checking, regardless of how much data there is
to check?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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-admin@postgresql.org
Cc: jnasby@pervasive.com, tgl@sss.pgh.pa.us, enzo@pienetworks.com
Subject: Re: Constraint question
In-Reply-To: <20060515151249.GE26212@pervasive.com>
References: <1147659556.29084.26.camel@localhost.localdomain> <21805.1147661450@sss.pgh.pa.us> <20060515151249.GE26212@pervasive.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