Message-ID: <25c101c362f8$9cdff400$2800a8c0@mars>
From: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
To: "Stephan Szabo" <sszabo@megazone.bigpanda.com>,
	"Gavin Sherry" <swm@linuxworld.com.au>
Cc: "Bruce Momjian" <pgman@candle.pha.pa.us>,
	"Peter Childs" <Blue.Dragon@blueyonder.co.uk>,
	"PostgreSQL-development" <pgsql-hackers@postgresql.org>
References: <20030814231203.P6635-100000@megazone.bigpanda.com>
Subject: Re: [GENERAL] 7.4Beta
Date: Fri, 15 Aug 2003 14:44:01 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> We've talked about stuff like that in the past, but we seem to generally
> get stuck about how to specify it.  If we add it to the alter table add as
> an option then we're generating statements that are almost like a standard
> sql statement, but not quite, and some people didn't like that. A set
> option that only affected ALTER TABLE ADD CONSTRAINT wouldn't be too bad,
> but I'd be worried about making it apply to the normal checks as well
> (which I believe was suggested last time this came up).  In any case,
> making the full checks faster for when you really do care isn't a bad
> plan. :)

Or, this:

1. Add the FK to the table BEFORE COPYing data
2. Use the old update blah set reltriggers = 0 trick
3. restore the data
4. Undo step 2

Chris