X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D3E259FA279 for ; Sun, 14 May 2006 23:46:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 86286-08 for ; Sun, 14 May 2006 23:46:10 -0300 (ADT) X-Greylist: delayed 00:19:13.002264 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 2812B9F946D for ; Sun, 14 May 2006 23:46:10 -0300 (ADT) Received: from mail.pienetworks.com (unknown [210.9.196.17]) by svr4.postgresql.org (Postfix) with ESMTP id 332FA5B1F74 for ; Mon, 15 May 2006 02:19:36 +0000 (GMT) Received: by mail.pienetworks.com (Postfix, from userid 521) id E813A5D411C; Mon, 15 May 2006 10:19:17 +0800 (WST) Received: from tuppy.pienetworks.com (tuppy.pienetworks.com [192.168.1.72]) by mail.pienetworks.com (Postfix) with ESMTP id BAC895D411B for ; Mon, 15 May 2006 10:19:15 +0800 (WST) Subject: Constraint question From: Enzo Daddario To: PGADMIN Content-Type: text/plain Date: Mon, 15 May 2006 10:19:16 +0800 Message-Id: <1147659556.29084.26.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/171 X-Sequence-Number: 21703 Hi All, I am currently using Postgres 8.1.2 and am in the process of restructuring our entire DB. The current structure - table "X" is the central/main table in the DB and has approx 100 tables which reference it in the form of foreign key constaints. 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. I am assuming that this is because the deletion of each row in table "X" requires that all the related tables(a number of them are huge) need to be first checked. Is there a way I can temporarily disable this checking and then re-enable it after the rows in table "X" are deleted. Thanks ENZO...