| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | XWorkers <xworkers(at)bangla(dot)net> |
| Cc: | Postgre General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: turning of referential integrity |
| Date: | 2000-08-12 23:46:45 |
| Message-ID: | Pine.BSF.4.10.10008121642500.76749-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
If you are using pg_dump, you probably should be fine if you're
restoring a full database, because it should place the constraints
in after the data is loaded. If you do a data only dump, there
is code in the dump at the very top and bottom to disable and
reenable the constraints and that should let you turn them off
and on -- however, you CANNOT define any triggers between those
two statements (let's just say it'd probably be bad).
Stephan Szabo
sszabo(at)bigpanda(dot)com
On Sat, 12 Aug 2000, XWorkers wrote:
> Hi All,
> I am wondering is there any way to turning off referential integrity
> without using SET CONSTRAINTS and create table with DEFERRABLE for database
> restore purpose?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-13 03:24:31 | Re: Locking |
| Previous Message | Tom Lane | 2000-08-12 17:45:46 | Re: [HACKERS] Optimizer confusion? |