| From: | kris pal <kristhegambler(at)yahoo(dot)com> |
|---|---|
| To: | Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: vacuum pg_attribute causes high load |
| Date: | 2004-08-28 12:32:11 |
| Message-ID: | 20040828123211.46039.qmail@web52809.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Before to do it be sure that your pg_dump is non affected by not well ordered
objects, if yes you have to reorder the order creation ( manually ) in the dump,
some times happen.
>>>>>>>>>>>>>>>>>>>>
I used the dump from the production database(bgms) and imported it into a test database (test). It went through fine with in few minutes. So I guess the ordering of the objects is fine. My only concern is abt the system catalog.
Do we need anything else from the original database "bgms" other than the Dump file to recreate it?
thanks,
Kris Pal.
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2004-08-28 14:28:16 | Re: Compatibility between different versions of psql client and postgresql server |
| Previous Message | Gaetano Mendola | 2004-08-28 10:21:33 | Re: vacuum pg_attribute causes high load |