| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Jan Lentfer <Jan(dot)Lentfer(at)web(dot)de>, Mel Llaguno <mllaguno(at)coverity(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <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 17:22:07 |
| Message-ID: | A76B25F2823E954C9E45E32FA49D70ECCD4520AE@mail.corp.perceptron.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Jan Lentfer
Sent: Monday, May 04, 2015 12:42 PM
To: Mel Llaguno
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] pg_dump and pg_restore with multiple streams does Not seem to improve overall times
I don't know about parallel pg_dump as we use -Fc and pg_dump can't do that in parallel (afaik). For dumping I have wrapped pg_dump in a shell script to dump several databases in parallel.
But for pg_restore -j option does make a big difference, at least when you have a lot of larger tables and indexes.
Regards,
Jan
Combination of -Fc and -j definitely works in pg_dump. And there is nothing in the docs that states otherwise.
Regards,
Igor Neyman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2015-05-04 17:28:33 | Re: migrating to 9.2 created blank dbs |
| Previous Message | Marc Fromm | 2015-05-04 17:14:06 | Re: migrating to 9.2 created blank dbs |