Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times - Mailing list pgsql-admin

From Jan Lentfer
Subject Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times
Date
Msg-id a37a287dd1d3a528f0d3a2a8b529f2a0@imap.lan.net
Whole thread Raw
In response to pg_dump and pg_restore with multiple streams does Not seem to improve overall times  ("Susan K. McClure" <smcclure@rice.edu>)
Responses Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times
List pgsql-admin
Am 2015-05-01 17:16, schrieb Susan K. McClure:

[...]
> My postgresql.conf has these options for (hopefully) pg_dump and
> pg_restore improvements:
>
> =================
> work_mem = 1GB # dump/restore Perf Value
> #maintenance_work_mem = 2048MB # min 1MB
> maintenance_work_mem = 1GB # dump/restore Perf Value
> #autovacuum_work_mem = -1 # min 1MB, or -1 to use
> maintenance_work_mem
>
> ...
> fsync = off # dump/restore Perf Valuecheckpoint_segments = 60 #
> dump/restore Perf Value
> checkpoint_warning = 60s # dump/restore Perf Value
> ......
> autovacuum = off # dump/restore Perf Value..
> =============================
>
> Any thoughts on what else I might try to improve things ?
[...]

It ist more interesting to know how your database schema is. How many
"large" tables do you have. What is e.g. the size of your 10,20,30
largest tables?

Regards

Jan





pgsql-admin by date:

Previous
From: Jan Lentfer
Date:
Subject: Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times
Next
From: Marc Fromm
Date:
Subject: Re: migrating to 9.2 created blank dbs