From: | Bob Lunney <bob_lunney(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org, Glen Brown <gkbrown22(at)gmail(dot)com> |
Subject: | Re: pg_dump/restore problems |
Date: | 2010-10-26 15:33:14 |
Message-ID: | 336456.89598.qm@web39705.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Glen,
Did you drop the indexes prior to the restore? If not, try doing so and recreating the indexes afterwards. That will also speed up the data load.
Bob Lunney
--- On Mon, 2/15/10, Glen Brown <gkbrown22(at)gmail(dot)com> wrote:
From: Glen Brown <gkbrown22(at)gmail(dot)com>
Subject: [ADMIN] pg_dump/restore problems
To: pgsql-admin(at)postgresql(dot)org
Date: Monday, February 15, 2010, 1:25 PM
I am not sure where I should post this but I am running into problems trying to restore a large table. I am running 8.4.1 on all servers. The table is about 25gb in size and most of that is toasted. It has about 2.5m records. When I dump this table using pg_dump -Fc it creates a 15 gb file. I am trying to restore in into a database that has 100gb of free disk space and it consumes it all and fails to finish the restore. The table is not partitioned and has a few indexes on it. What can I do?
thanks
-glen
Glen Brown
From | Date | Subject | |
---|---|---|---|
Next Message | Maria L. Wilson | 2010-10-26 15:33:44 | postgres 8.4.5 jdbc is 8.4-701.jdbc3 |
Previous Message | Martin Povolny | 2010-10-26 11:41:44 | large database: problems with pg_dump and pg_restore |