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

> > 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
>
> The problem with that is that I think the reltriggers=0 trick only works
> if you're superuser, I thought that's why the trigger disabling became
> optional.  A set that affected only atac would probably be reasonable in
> the dump (and presumably easy to do).  It'd also carry over to future
> cases where we separate some check constraints (for examples ones
> that refer directly or indirectly to the same table in a subselect).

Well yes, this would be a super-user only ability.  Are you worried about
people restoring dumps as non-superuser?

Chris