X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id EF6B85E40BA
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Sat, 21 Aug 2004 21:42:07 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 79547-05
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Sun, 22 Aug 2004 00:42:04 +0000 (GMT)
Received: from yobe.org (p15112446.pureserver.info [217.160.168.103])
	by svr1.postgresql.org (Postfix) with ESMTP id B89955E40AC
	for <pgsql-sql@postgresql.org>; Sat, 21 Aug 2004 21:42:02 -0300 (ADT)
Received: from pd9e725b6.dip.t-dialin.net ([217.231.37.182]
	helo=[192.168.1.197])
	by yobe.org with asmtp (TLS-1.0:DHE_RSA_AES_128_CBC_SHA:16)
	(Exim 4.34) id 1BygQo-0003rF-Ga
	for pgsql-sql@postgresql.org; Sun, 22 Aug 2004 02:42:18 +0200
Message-ID: <4127EBBF.2040405@yobe.org>
Date: Sun, 22 Aug 2004 02:41:35 +0200
From: Roman Kunert <rkunert@yobe.org>
User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040805)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: disable constrained (contd.)
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200408/233
X-Sequence-Number: 18730

I just wanted to know if there is an update to the topic

http://archives.postgresql.org/pgsql-sql/2003-02/msg00624.php

I am also looking for an easy way to disable foreign key constraint 
check while importing data from one database to PostgreSQL. The one 
suggested method (see link above) that modifies pg_catalog.pg_class is 
not preferrable, as it requires super user rights, the other one that 
works by dropping the foreign key, doing the inserts and then adding it 
back again does not seem to work, as it results in an constraint check 
error when I execute the ADD statement (it complains about the reference 
to a row in another table that has not been imported yet, but will be 
later during the import)

any news on this? thanks.