pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Enzo Daddario <enzo@pienetworks.com>
Cc: PGADMIN <pgsql-admin@postgresql.org>
Subject: Re: Constraint question
Date: Mon, 15 May 2006 11:17:31 -0400
Message-ID: <3260.1147706251@sss.pgh.pa.us> (raw)
In-Reply-To: <20060515151249.GE26212@pervasive.com>
References: <1147659556.29084.26.camel@localhost.localdomain>
	<21805.1147661450@sss.pgh.pa.us>
	<20060515151249.GE26212@pervasive.com>

"Jim C. Nasby" <jnasby@pervasive.com> writes:
> 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?

It's the same machinery.  We've speculated about having the thing switch
over to doing a full-table recheck (comparable to what ADD CONSTRAINT
FOREIGN KEY does) once the number of pending individual row checks
exceeds some threshold, but that's not done yet --- and it's not clear
how to do it in a concurrent fashion, so don't hold your breath ...

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <3260.1147706251@sss.pgh.pa.us>
Permalink:  ../3260.1147706251@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3260.1147706251@sss.pgh.pa.us

 · 

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jnasby@pervasive.com, enzo@pienetworks.com
  Subject: Re: Constraint question
  In-Reply-To: <3260.1147706251@sss.pgh.pa.us>
  References: <1147659556.29084.26.camel@localhost.localdomain> <21805.1147661450@sss.pgh.pa.us> <20060515151249.GE26212@pervasive.com> <3260.1147706251@sss.pgh.pa.us>

* 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