Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times

From: Jan Lentfer <Jan(dot)Lentfer(at)web(dot)de>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times
Date: 2015-05-04 12:17:14
Message-ID: a37a287dd1d3a528f0d3a2a8b529f2a0@imap.lan.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Marc Fromm 2015-05-04 14:59:21 Re: migrating to 9.2 created blank dbs
Previous Message Jan Lentfer 2015-05-04 12:14:01 Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times