| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: parallel pg_restore |
| Date: | 2008-09-22 10:04:09 |
| Message-ID: | 1222077849.4445.150.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2008-09-22 at 09:53 +0200, Dimitri Fontaine wrote:
> > My intention is to have single-thread restore remain the default, at
> > least for this go round, and have the user be able to choose
> > --multi-thread=nn to specify the number of concurrent connections to use.
>
> What about the make famous -j option?
>
> -j [jobs], --jobs[=jobs]
> Specifies the number of jobs (commands) to run simultaneously. If
> there is more than one -j option, the last one is effective. If
> the -j option is given without an argument, make will not limit
> the number of jobs that can run simultaneously.
+1
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-09-22 10:08:44 | Re: parallel pg_restore |
| Previous Message | Simon Riggs | 2008-09-22 10:02:16 | Re: Initial prefetch performance testing |