From: | "Chris White (cjwhite)" <cjwhite(at)cisco(dot)com> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Problems doing a restore under 7.4.2 |
Date: | 2004-04-22 06:45:27 |
Message-ID: | 00aa01c42835$660f6840$0300a8c0@amer.cisco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I got around the problem by using the --disable-triggers option on the
restore.
Chris
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, April 21, 2004 9:02 PM
To: cjwhite(at)cisco(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Problems doing a restore under 7.4.2
"Chris White (cjwhite)" <cjwhite(at)cisco(dot)com> writes:
> I have done a backup of my 7.4.2 database using pg_dump. When I
> restore the database using the -c option I get the following error
> message and pg_restore fails
> pg_restore: [archiver (db)] could not execute query: ERROR: trigger
> "RI_ConstraintTrigger_17371" for table "vm_message" does not exist
Probably an ordering issue --- easiest workaround is not to use -c, I'd
think.
If you like, you could try CVS-tip pg_dump to see if it gets the
ordering right.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fischer Ulrich | 2004-04-22 08:55:06 | Restoring a Databases that features tserach2 |
Previous Message | Tom Lane | 2004-04-22 04:25:29 | Re: set_curcfg('default') + tsearch1 call = postmaster crash |