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: Igor Neyman <ineyman(at)perceptron(dot)com>,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 18:03:07
Message-ID: 0B05EA0E-40EF-4401-B473-B28394918E71@web.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Am 4. Mai 2015 19:22:07 MESZ, schrieb Igor Neyman <ineyman(at)perceptron(dot)com>:
>
>
>-----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

Well, the manual says

You can only use this option with the directory output format because this is the only output format where multiple processes can write their data at the same time.

For the -j Option

Regards

Jan

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Igor Neyman 2015-05-04 18:25:53 Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times
Previous Message Marc Fromm 2015-05-04 17:58:56 Re: migrating to 9.2 created blank dbs