| From: | ow <oneway_111(at)yahoo(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_restore and FK constraints with large dbs |
| Date: | 2003-11-16 16:45:44 |
| Message-ID: | 20031116164544.72117.qmail@web21405.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
--- Peter EiEisentrautpeter_e(at)gmgmxet> wrote:
>
> Read again. No one was talking of pg_restore.
Perhaps I should clarify.
First, I ran pg_dump to extract schema and data *together*. Then I ran
pg_restore to restore the db. It took about 1 hour to create tables and copy
the data, then about 40 min to create indexes, then pg_restore spent 4.5 hours
checking one (1) FKFKonstraint (80M table with FKFKsgainst 20K table with PKPKs
4.5 hours to check one FKFKonstraint - this is want I meant by bad performance.
I'm looking for a way to suspend FKFKhecks since data is coming from pg_dump
and, hence, it's clean.
Thanks
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oli Sennhauser | 2003-11-16 17:26:38 | Re: pg_restore and FK constraints with large dbs |
| Previous Message | Peter Eisentraut | 2003-11-16 15:19:46 | Re: pg_restore and FK constraints with large dbs |