| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Stephan Szabo" <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | "Gavin Sherry" <swm(at)linuxworld(dot)com(dot)au>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Peter Childs" <Blue(dot)Dragon(at)blueyonder(dot)co(dot)uk>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] 7.4Beta |
| Date: | 2003-08-15 07:17:21 |
| Message-ID: | 262601c362fd$4ee2f310$2800a8c0@mars |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> > 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-08-15 07:32:01 | Re: importing db as text files |
| Previous Message | Stephan Szabo | 2003-08-15 06:58:59 | Re: [GENERAL] 7.4Beta |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-08-15 07:33:59 | Re: [GENERAL] 7.4Beta |
| Previous Message | Stephan Szabo | 2003-08-15 06:58:59 | Re: [GENERAL] 7.4Beta |