| From: | David Kerr <dmk(at)mr-paradox(dot)net> |
|---|---|
| To: | "Burgholzer, Robert (DEQ)" <Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: proper tuning for restoring from pg_dump in 8.3.7 |
| Date: | 2010-07-14 21:35:33 |
| Message-ID: | 20100714213533.GA43630@mr-paradox.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Jul 14, 2010 at 05:30:17PM -0400, Burgholzer, Robert (DEQ) wrote:
- >. The options I suggested be turned off just for the load process
- > ...
- > not safe if the other databases are in the same PostgreSQL Cluster
-
- They are, so I won't --- thanks for the heads up on that too.
-
- Just for posterity, here is the systems specs (from my hardware guy):
- DEQ1 is on centos 5.3
- W/ 1.5Tb striped system volumes using a pair of standard 7600 rpm sata
- drives. These are on system 3 gbit/s ports.
So that makes total sense. you're flooding your disks/controller doing
the massive amount of writing that's involved with the restore.
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karma Bhutia | 2010-07-15 07:28:32 | Urgent - MySQL Postgres DBA - CA |
| Previous Message | Burgholzer, Robert (DEQ) | 2010-07-14 21:30:17 | Re: proper tuning for restoring from pg_dump in 8.3.7 |