| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Heading to final release |
| Date: | 2003-10-14 00:07:05 |
| Message-ID: | 1066090024.46588.11.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >> > Allow superuser (dba?) the ability to turn off foreign key checks/all
> >> > constraints/triggers, not settable from postgresql.conf?
> >>
> >> Is that one really necessary for 7.4 now that adding foreign keys is
> >> apparently much faster?
> If you reconfigure your systems to force fsck on every boot, cleanly
> unmounted or not, you can vote against. Otherwise you are basically for
> this option.
I vote to disable the checks for pg_restore if the dumpfile has a check
added to ensure it's the same file that was dumped (an MD5 in the
header) and it is a full database restore.
Individual table restores should require the check.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2003-10-14 00:11:08 | Re: 2-phase commit |
| Previous Message | Tom Lane | 2003-10-14 00:01:55 | Re: ways to force index use? |