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-13 23:02:51 |
Message-ID: | 20031113230251.64140.qmail@web21409.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
--- Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> ow writes:
>
> > 1) dump the data only, create the table with all indexes and constraints
> (from
> > script that has nothing to do with pg_restore), import the data. The import
> > part was running for hours (14+) with no end in sight. Had to kill it.
>
> Dump the data and the schema and it will do it in the right order.
Can you clarify how this would be better than the second option I described?
Unless pg_restore can somehow create FK constraints differently (and more
efficiently) than using "ALTER TABLE xxx ADD CONSTRAINT", I do not see how this
would help.
Thanks
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-11-13 23:44:37 | Re: pg_restore and FK constraints with large dbs |
Previous Message | Ajay Prabhakar | 2003-11-13 22:45:27 | Modify a database user |