From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Gavin Sherry <swm@linuxworld.com.au>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Peter Childs <Blue.Dragon@blueyonder.co.uk>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [GENERAL] 7.4Beta
Date: Fri, 15 Aug 2003 15:17:21 +0800
Message-ID: <262601c362fd$4ee2f310$2800a8c0@mars> (raw)
References: <20030814233926.D8240-100000@megazone.bigpanda.com>
> > 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
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: chriskl@familyhealth.com.au, sszabo@megazone.bigpanda.com, swm@linuxworld.com.au, pgman@candle.pha.pa.us, Blue.Dragon@blueyonder.co.uk
Subject: Re: [GENERAL] 7.4Beta
In-Reply-To: <262601c362fd$4ee2f310$2800a8c0@mars>
* 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